Database Users

[Problem] Notifications & Sounds Menu Bug

Hi,
The problem:
When entering the notifications & sounds menu in wm 6.5.5 the right ringtone shows up, when choosing another one and playing it, no problem occurs. But when I want to exit the dialog via OK, all ringtones in the menus are skipped through until the default windows-ring01 ringtone is on top of the list. The dialog is not closing that way, cause every time I want to, the whole skipping happens again and the default ringtone is set.
I used the search quite excessively, but didn't find a solution. I know I came across this error before and I'm pretty sure I was able to fix it, but I have no idea how.
Anybody able to point me in the right direction?
thanks

Do you have a native kernel (WM6.5) or non native kernel (WM6.1)? If it is non native, then recmod browsingie files, and the error should go away...

Did you cook in DRMMiddleware? Maybe other DRM packages are also needed.

That usually happens when you have DRM packages cooked in. Remove them...

This happened to me and my Kaiser when i tried to build a rom with different SYS and MXIPKernel.....hope this aint your situation.

Thanks for the hints! I switched to other SYS & XIP - its working fine now.
Just for clarification:
- Native 6.5
- DRM is build in right now
So it seems it was the different XIP and SYS I was using.

Narrowed it down to the boot.rgu and boot.hv files in the XIP. Didn't take a closer look, but I can say for sure that some setting in there is causing the bug.

chalid said:
Narrowed it down to the boot.rgu and boot.hv files in the XIP. Didn't take a closer look, but I can say for sure that some setting in there is causing the bug.
Click to expand...
Click to collapse
That's where some of the DRM codecs get referenced. Most likely the one you had before, had those references removed

this can be fixed by adding "MediaOSModules" package to sys from another sys from the same com build,and deleting "MediaOSFiles" package from sys.

In some cases if I add mediaos files as modules, then utube will not play. But it plays fine with them as files!

[Problem] [ERROR]Please check HTCLOG

I recently updated my OSKitchen from 1.26 to 1.30/1alpha only to find that now when I cook a ROM I get the [ERROR]Please check HTCLOG message on bootup. I updated a few EXT packages at the same time but nothing critical - my OEM and SYS are untouched from when my ROM's were working just fine under OSK 1.26.
Any ideas what's causing this error message? It was suggested by someone that my RunCC may be calling config.txt files with faulty values in them, but I've checked the config's and all seems fine (only modification by me is to use amarullzgreenblack.tsk instead of classicblue.tsk and this is untouched from previous working ROMs).
Really don't want to have to rebuild the damned kitchen from scratch

millski said:
I recently updated my OSKitchen from 1.26 to 1.30/1alpha only to find that now when I cook a ROM I get the [ERROR]Please check HTCLOG message on bootup. I updated a few EXT packages at the same time but nothing critical - my OEM and SYS are untouched from when my ROM's were working just fine under OSK 1.26.
Any ideas what's causing this error message? It was suggested by someone that my RunCC may be calling config.txt files with faulty values in them, but I've checked the config's and all seems fine (only modification by me is to use amarullzgreenblack.tsk instead of classicblue.tsk and this is untouched from previous working ROMs).
Really don't want to have to rebuild the damned kitchen from scratch
Click to expand...
Click to collapse
Normally it will point you to the culprit. You need to check all the config txt's ie config_ap, config_operator, etc. It could be a bad cab, xml, tsk, etc being called up by one of the config txt's.

TMartin03 said:
Normally it will point you to the culprit. You need to check all the config txt's ie config_ap, config_operator, etc. It could be a bad cab, xml, tsk, etc being called up by one of the config txt's.
Click to expand...
Click to collapse
There's no information in the box that appears other than the error message, so no clues as to what's failing. Having checked all my config files from the runcc.lua the only thing that is called at all is the amarullzgreenblack.tsk, which is being cooked in and as I said it's been working fine for my last 5 or 6 roms without change.
The only thing I've noticed is that the older OSK I was using (1.26) sorted some packages containing config.txt's into the OEM dir, while the new OSK puts them into EXT. Folder structure is then different and I think it must be this that's broken it. I've tried rebuilding the OEM's as EXT's but it still won't work

millski said:
There's no information in the box that appears other than the error message, so no clues as to what's failing. Having checked all my config files from the runcc.lua the only thing that is called at all is the amarullzgreenblack.tsk, which is being cooked in and as I said it's been working fine for my last 5 or 6 roms without change.
The only thing I've noticed is that the older OSK I was using (1.26) sorted some packages containing config.txt's into the OEM dir, while the new OSK puts them into EXT. Folder structure is then different and I think it must be this that's broken it. I've tried rebuilding the OEM's as EXT's but it still won't work
Click to expand...
Click to collapse
Try changing the tsk thats called up by config.txt to one Classic Blue or something other than amarullzgreenblack.tsk just to rule that out.

TMartin03 said:
Try changing the tsk thats called up by config.txt to one Classic Blue or something other than amarullzgreenblack.tsk just to rule that out.
Click to expand...
Click to collapse
Tried that, still wouldn't work. If I cook without RunCC the ROM will boot without error, but then the initial customisation doesn't run i.e. no SIM or operator settings are made.
I don't think I'm going to get to the bottom of this so I've started building a new kitchen. Does anyone know which packs from Leo 2.14 will make my ROM TMOUS HD2 compatible? I can't remember...

[SOLVED] Launching camera gives an error..

Hi again guys! I have this problem with the rom i'm customizing. Everytime I launch the camera it says "Unable to start camera. Not enough memory"...
I'm new to cooking and I'm still in the learning process. Please help me with this. Thanks!

What taskmanager are you using? If standard HTC taskmanager, try this:
[HKEY_CURRENT_USER\Software\HTC\TaskManager]
"SkipAK4Camera"=dword:00000000

What device are you cooking for and which camera are you using?
pongskie said:
Hi again guys! I have this problem with the rom i'm customizing. Everytime I launch the camera it says "Unable to start camera. Not enough memory"...
I'm new to cooking and I'm still in the learning process. Please help me with this. Thanks!
Click to expand...
Click to collapse

Laurentius26 said:
What device are you cooking for and which camera are you using?
Click to expand...
Click to collapse
I'm cooking a rom for a Leo, i use Camera v6.26.20121425.00..
still can't figure this out..
When i tried to make a new kitchen and copy all my ext there the camera launches but the restart after customization on first boot is not working anymore. I'm search for fixes with this or anything related but still no luck.

Sorry I don't understand mate, you launch the camera while device customisation isn't done yet?
If it's caused by device customisation I would have a closer look at the provxmls if they contain some camera presets.
First packages I would check are:
* Operatorpkg
* ProjectDefault_A
* ProjectDefault_B
* ProjectDefault_C
Another check is ExtendedPkg - config.txt to see if there isn't a .cab launched which could cause this.
Also I don't know if you are using a mixture of packages but try to keep them as much as possible from one source.
pongskie said:
I'm cooking a rom for a Leo, i use Camera v6.26.20121425.00..
still can't figure this out..
When i tried to make a new kitchen and copy all my ext there the camera launches but the restart after customization on first boot is not working anymore. I'm search for fixes with this or anything related but still no luck.
Click to expand...
Click to collapse

Laurentius26 said:
Sorry I don't understand mate, you launch the camera while device customisation isn't done yet?
If it's caused by device customisation I would have a closer look at the provxmls if they contain some camera presets.
First packages I would check are:
* Operatorpkg
* ProjectDefault_A
* ProjectDefault_B
* ProjectDefault_C
Another check is ExtendedPkg - config.txt to see if there isn't a .cab launched which could cause this.
Also I don't know if you are using a mixture of packages but try to keep them as much as possible from one source.
Click to expand...
Click to collapse
Sorry Sir Laurentius26 if I'm not clear. After flashing my cooked rom, I tried to test if the camera is working but then when i tried to open it the error pop up telling "Unable to start camera. Not enough memory".
I got the the ext package from the later rhodium pack but the camera wont work if i used the one that was added from there so i replaced it with the one from 3.02 ext pkgs. I really got confused with this because it's my first time to cook a rom for leo. As of now I'm still reading things about cooking.
Sorry for all of this, I really am new to this.

No problem and you don't have to say 'Sir' amigo.
I'm only trying to point you in the right direction.
What you can do is check the config.txt I suggested and see what's in there.
The provxmls you can compair with a stock working Leo rom.
I use a application named 'compair it' to do that.
You can compair bought provxmls side by side and see if there are any differences in camera presets.
http://www.grigsoft.com/wincmp3.htm
About the packages from Rhodium, experiment and replace the multimedia ones as well with the 3.02 source you have.
It's just quesing for me but maybe the following:
* MHub
* Media Toolkit
* DShow
* Picture Enhancement
* App Service
* HTC Application
* HTCUtil
* Power
* PowerOffwarning
* SensorSDK
* Resourceproxy
I've had the same problem as you with the camera in past but unfortunatly I don't remember what it was.
Did you apply tweaks to the camera which could cause out of memory issues?
pongskie said:
Sorry Sir Laurentius26 if I'm not clear. After flashing my cooked rom, I tried to test if the camera is working but then when i tried to open it the error pop up telling "Unable to start camera. Not enough memory".
I got the the ext package from the later rhodium pack but the camera wont work if i used the one that was added from there so i replaced it with the one from 3.02 ext pkgs. I really got confused with this because it's my first time to cook a rom for leo. As of now I'm still reading things about cooking.
Sorry for all of this, I really am new to this.
Click to expand...
Click to collapse

Laurentius26 said:
No problem and you don't have to say 'Sir' amigo.
I'm only trying to point you in the right direction.
What you can do is check the config.txt I suggested and see what's in there.
The provxmls you can compair with a stock working Leo rom.
I use a application named 'compair it' to do that.
You can compair bought provxmls side by side and see if there are any differences in camera presets.
http://www.grigsoft.com/wincmp3.htm
About the packages from Rhodium, experiment and replace the multimedia ones as well with the 3.02 source you have.
It's just quesing for me but maybe the following:
* MHub
* Media Toolkit
* DShow
* Picture Enhancement
* App Service
* HTC Application
* HTCUtil
* Power
* PowerOffwarning
* SensorSDK
* Resourceproxy
I've had the same problem as you with the camera in past but unfortunatly I don't remember what it was.
Did you apply tweaks to the camera which could cause out of memory issues?
Click to expand...
Click to collapse
Yes i have applied some tweaks but it was working before then suddenly it didn't. I think i know why this happened. Before the error occurs, I have read about sys packages that you can recmod so I tried it. After that I found the bug with all ringtones, my rom doesnt recognize ringtones anymore. Back then I try removing the recmods from my kitchen, btw i'm using OsKitchen, so i uncheck the ones that i have recmodded. After that the error occurred. I saw only now that there's a recmod cache. I tried to replace it with the fresh recmod cache that only contains the needed recmods to boot the rom. I'm still building the rom now and will flash and check if the error is still there. I'll update here whatever I found out after.

Ringtone problems and camera problems are mostly caused by the wrong Dshow.
Don't use recmodding to much and keep everything modulair as it's.
pongskie said:
Yes i have applied some tweaks but it was working before then suddenly it didn't. I think i know why this happened. Before the error occurs, I have read about sys packages that you can recmod so I tried it. After that I found the bug with all ringtones, my rom doesnt recognize ringtones anymore. Back then I try removing the recmods from my kitchen, btw i'm using OsKitchen, so i uncheck the ones that i have recmodded. After that the error occurred. I saw only now that there's a recmod cache. I tried to replace it with the fresh recmod cache that only contains the needed recmods to boot the rom. I'm still building the rom now and will flash and check if the error is still there. I'll update here whatever I found out after.
Click to expand...
Click to collapse

Laurentius26 said:
Ringtone problems and camera problems are mostly caused by the wrong Dshow.
Click to expand...
Click to collapse
OK that's noted mate! Will let you know what happens after flashing the rom. Still waiting for it to finish building.
Thanks!

After removing the recmod cache, still when i try to launch the camera it says that there's not enough memory. I will try to replace the Dshow with the one from 3.02 ext pack.

But your rom still boots isn't?
DShow is more important then the recmodding as it contains the codecs to play your audio and video files.
I don't understand why you didn't follow my advise in the first place, it would have saved you another flash.
pongskie said:
After removing the recmod cache, still when i try to launch the camera it says that there's not enough memory. I will try to replace the Dshow with the one from 3.02 ext pack.
Click to expand...
Click to collapse

Laurentius26 said:
But your rom still boots isn't?
DShow is more important then the recmodding as it contains the codecs to play your audio and video files.
I don't understand why you didn't follow my advise in the first place, it would have saved you another flash.
Click to expand...
Click to collapse
The rom still boot, everything works fine except for the following:
I try replacing the dshow but still the problem is there. And also when I type from the keyboard there are no words in the suggested word box when XT9 is activated.
Also when I go to All settings>Personal>Buttons.. there are no buttons to assign. I have included the reg keys for removing the redirect but still there are no buttons to assign there.
If still the problem is there, I think i need to make a new one and start from scratch again. I'm running out of ways to try to fix this.
and btw, was the number of times you flashed a rom in your phone is affecting it? or does it have any effects?

Are the ringtones working?
I asume that you use a Leo dialer and not the Rhodium?
Go back to my previous post with suggested packages and replace them with the 3.02.
If your rom boots why should you start all over again?
About your last question.
Wild ques 5 times a day x 365 days.
It doesn't affect, I'm cooking for about 8 years now.
I must go now, goodluck and I will check later your progress.
pongskie said:
The rom still boot, everything works fine except for the following:
I try replacing the dshow but still the problem is there. And also when I type from the keyboard there are no words in the suggested word box when XT9 is activated.
Also when I go to All settings>Personal>Buttons.. there are no buttons to assign. I have included the reg keys for removing the redirect but still there are no buttons to assign there.
If still the problem is there, I think i need to make a new one and start from scratch again. I'm running out of ways to try to fix this.
and btw, was the number of times you flashed a rom in your phone is affecting it? or does it have any effects?
Click to expand...
Click to collapse

Laurentius26 said:
Are the ringtones working?
I asume that you use a Leo dialer and not the Rhodium?
Go back to my previous post with suggested packages and replace them with the 3.02.
If your rom boots why should you start all over again?
About your last question.
Wild ques 5 times a day x 365 days.
It doesn't affect, I'm cooking for about 8 years now.
I must go now, goodluck and I will check later your progress.
Click to expand...
Click to collapse
Thanks mate! I'll try to fix this! I'll keep you posted here what will happen next.

After trying a couple of times the problem still exist. I have tried to make a new kitchen but then the "Unable to start camera. Not enough memory" error appeared again. I think it's in my reg tweaks. I'll try not to add those and see that happens.

It is confirmed. The error was triggered by the reg keys that I have included. Still trying to find out which one of the reg keys are doing it.
Edit: After adding few apps, the error was there again. I'll try to figure out what really causes this problem.... As of now still unsolved..

Solution..
Laurentius was right, I got the camera working but I have remake my kitchen first before it worked. By the time I compiled everything in my new kitchen, I tried my very best to keep everything from one source. Then slowly one by one replacing what needs to be replaced.
I got all the apps and the reg edits in and the camera is still working.
Just always be careful in adding tweaks, that's also one of the main reason why the camera didn't launch.
This gives a clear solution to the problem mention in the thread Title.
Thanks,
Pongskie
Thanks to Sir Laurentius26!
Edit: I will change the title of the thread to solved now.

HD2 Leo 3.14 Custom ROM freezing after standby

I have build a custom hd2 rom with oskitchen and xip/sys 28244.
It's working very well.
Now I have added some ext packages found here that seems to be useful. And now the new rom has the following issue: After leo goes to standby by itsself or by pressing the off key and some time later it will not wake up. Buttons are lightened but screen stays black. I have to put the battery out or to reset. Than rom is working again until next standby.
It happens only, if device is in standby for some time. If you press off and then wake up device immediately, all is working well.
Any idea, if this can be result of some added package or some component of the xip/sys build?

Have now found out something:
If I remove the following ext packages from my built rom, the rom works without freezing after going to standby:
HTC Tweaks
AMEBA
Opera Mini 5.1
Google Maps 4.1.1
But If I install those apps as cabs, the rom is working well after installation.
Can it be that they conflict with some built-in package of leo which causes the freezing issue, which is not there if installing the packages?

thunder141, not sure what you mean by HTC Tweaks but if you increased system cache (as it proposed to do somewhere in Leo related threads) to absolutely huge unacceptable meaning - your phone just tries to cache memory...
Get rid of that tweak, or check your Storage Card (maybe format will help) - possibly the system is trying to cache to it and it's fragmented or just too slow....

i mean the app hd2 tweak with standard configuration converted to an ext from the cab

thunder141, am I supposed to know what does that mean - "app hd2 tweak with standard configuration "?
I tweak my roms by myself and never try to have fun with someone's "tweaks compilations"
Can you be more specific? Give me a link to the cab or attach your package for me to have a look.....

sorry ;-) I thought it is a known prog cause i found it here at xda.
http://forum.xda-developers.com/showthread.php?t=452505
But I misspelled it. Its hd tweak not hd2 tweak.
I imported the cab with oskitchen's import feature. And when I cook it in, my rom freezes after going to standby. If left it out, rom works fine.
I attach the ext, oskitchen created for me

Its not a spelling problem but the fact that those tweaks are made for HTC HD not HD2.
I suggest you to dont use it, simple solution.
thunder141 said:
sorry ;-) I thought it is a known prog cause i found it here at xda.
http://forum.xda-developers.com/showthread.php?t=452505
But I misspelled it. Its hd tweak not hd2 tweak.
I imported the cab with oskitchen's import feature. And when I cook it in, my rom freezes after going to standby. If left it out, rom works fine.
I attach the ext, oskitchen created for me
Click to expand...
Click to collapse

af974 said:
Its not a spelling problem but the fact that those tweaks are made for HTC HD not HD2.
I suggest you to dont use it, simple solution.
Click to expand...
Click to collapse
No, at his page there are hd tweak for other device and hd2 tweak for hd2 (leo). (http://www.montecristoff.com/hd2tweak.htm)
But, as I said, its not only this ext pkg but the others mentioned make my device freeze, too. And if used by cab install, not. And I do not understand the difference for those apps, if they worked when not cooked in.
I decided to put them in my uc_net folder for now and left them out of my rom, so my device won't freeze

before my hd2 got bricked due to my stupidity, i was trying to find solution to freezing issues.
i found out that if cad.dll and wavedev.dll are excluded, no death occurs after sleep. (of course, these dlls are vital for sound, so we cannot exclude them).
so my suggestion would be to first exclude these 2 dlls and include your packages to see if this clash is causing problem and then find compatible version of your packages with these 2 dlls or find compatible dll.
personally, i think these 2 dll have some odd bug with certain versions of windows system.

[SOLVED] Initflashfile.dat problem: device frozen until taskbar is pressed.

Hi,
I've been facing the following problem on my ROM: After a fresh flashing or hard reset, the device is unresponsible, and the start menu does not start and subsequently Manila doesn't start, until the taskbar is pressed.
Any ideas?
could it be something on the kitchen (osKitchen Zero 1.33.5) or OEM packages?
EDIT 4/OCT:
Solved.
I've started from scratch using LEO 3.14 initflashfiles and removing/changing only the necessary, and testing after each change.
Saved as Unicode UTF-16 with CR+LF (first 4 digits removed with HEX editor)
I didn't removed/changed the links that didn't create a shortcut. Only those which were creating links on the wrong place.
EDIT 1/Oct:
After rebuilding my whole kitchen, found the problem is related to Initflashfile.dat.
The dumped initflashfile.dat works without problems, but when I modify it, the problem appear.
I was editing using notepad2.
After found the problem, I searched the forum and found that after modification it needs to be HEXedited removing 4 first digits:
4. Install Hex Workshop Trial if you havent already. Open initflashfiles.dat in the hex editor.
The first 4 digits should say FFFE or something like this. Highlight those first 4 numbers and right click and delete. This is the header written in by notepad. This HAS to be removed for you initflashfiles.dat to work correctly. Then save.
Click to expand...
Click to collapse
But even after removing these digits I still have the problem.
Can someone give me some advise about how to modify the Initflashfile.dat?
I've attached the 2 files for your reference.
Thanks in advance.
Brgds

I use LockScreen from Huasan in COM3 without problems. It also may interact with your lockdevice 1.6 and you must put out Lock Screen App Launcher from Leo. Perhaps is this. I had this issue but I don´t remember why was. Sometimes was custom icons or backgrounds like "StartMenu_Background_Screen_480x800.png" & "StartMenu_Background_Screen_800x480.png". I didn´t be able to change these png´s. Get Lucky

This issue is driving me crazy.
I've just cook a ROM witout any external package only Sys and OEM and the problem is still there.
Also checked with a COM 2 build and the same issue.
I'm using osKitchen Zero v1.33.5, I've tried reimporting the original ROM and recoocking it with the same issue.
Any idea what else I can check?
Could it be a kitchen related problem?

I would suggest cooking with a different kitchen, but same pkgs and see if there is an issue. Sometimes kitchens do cause bugs...

Hi,
Finally managed to find what file was producing the problem.
I modified the first post and attached the files.
Hope someone can help me!
thanks in advance.