When trying to add Sense 2.5 to my upcoming CDMA TP2 ROM, I found that my ROM would freeze just as RunCC was launching. By removing RunCC, that issue was resolved.
Now I am having an issue where Sense 2.5 will not launch. The screen flashes several times, and eventually goes to "Tap here to launch Sense". Also, which I believe may be related, dialer screen will not come up when hitting the green phone button. It works if I roll back to the MR1 dialer, which is why I suspect that the two issues are connected.
I've never cooked with Sense, so hopefully I am just missing something really simple. I verified that the "IsWM6.5" key is set correctly.
Are you using sense as it is or have any mods?
I took the EXT packages directly from the Verizon MR2 ROM update. I have not modified any parts of it.
NotATreoFan said:
I took the EXT packages directly from the Verizon MR2 ROM update. I have not modified any parts of it.
Click to expand...
Click to collapse
What about the initflashfiles?
cnzqy1 said:
What about the initflashfiles?
Click to expand...
Click to collapse
That was the problem! I didn't realize there were so many lines in InitFlashFiles that controlled Sense.
Of course, now that Sense loads correctly, I can't get the dialer to work. When I press the Send key, nothing happens. I'm sure that it's just a shortcut missing, but I cannot pinpoint it.
-Edit-
Phone_Canvas_Enhancement_4_2_54620113831_0 does not work, but Phonecanvas_MASD_3_40_35786_0 does.
Do you have any dialer mods that overwrites the phonecanvas files?
ai6908 said:
Do you have any dialer mods that overwrites the phonecanvas files?
Click to expand...
Click to collapse
Not that I am aware of. I've uploaded the files below. If I use the packages in the "working" folder, the dialer is OK. If I use the other packages, the dialer will not open when I hit any keys.
Related
Hi Guys,
I'm using the Dusk theme and bars etc.. Once I'd installed I noticed that the Pop Out scroll bar had vanished. This I thought was an extremeeeeeely useful setting....
So I hard reset and dumped the today reg from HKCU, after a little messing about figured that I'd just import the reg keys from the original settings. Here are the keys
[HKEY_CURRENT_USER\Software\Microsoft\Today\ScrollBar]
"ScrollBarThumbThemeImage"="\\Windows\\HTCblack_scrollbarThumb.png"
"ScrollBarThumbThemeImageBottomMargin"=dword:00000022
"ScrollBarThumbThemeImageLeftMargin"=dword:00000008
"ScrollBarThumbThemeImageRightMargin"=dword:00000008
"ScrollBarThumbThemeImageTiled"=dword:00000000
"ScrollBarThumbThemeImageTopMargin"=dword:00000022
"ScrollBarTrackThemeImage"="\\Windows\\HTCblack_scrollbarTrack.png"
"ScrollBarTrackThemeImageBottomMargin"=dword:00000000
"ScrollBarTrackThemeImageLeftMargin"=dword:00000000
"ScrollBarTrackThemeImageRightMargin"=dword:00000000
"ScrollBarTrackThemeImageTiled"=dword:00000000
"ScrollBarTrackThemeImageTopMargin"=dword:00000000
"ScrollBarUpArrowButtonDisabledThemeImage"=""
"ScrollBarUpArrowButtonDisabledThemeImageBottomMargin"=dword:00000000
"ScrollBarUpArrowButtonDisabledThemeImageLeftMargin"=dword:00000000
"ScrollBarUpArrowButtonDisabledThemeImageRightMargin"=dword:00000000
"ScrollBarUpArrowButtonDisabledThemeImageTiled"=dword:00000000
"ScrollBarUpArrowButtonDisabledThemeImageTopMargin"=dword:00000000
"ScrollBarUpArrowButtonSelectedThemeImage"=""
"ScrollBarUpArrowButtonSelectedThemeImageBottomMargin"=dword:00000000
"ScrollBarUpArrowButtonSelectedThemeImageLeftMargin"=dword:00000000
"ScrollBarUpArrowButtonSelectedThemeImageRightMargin"=dword:00000000
"ScrollBarUpArrowButtonSelectedThemeImageTiled"=dword:00000000
"ScrollBarUpArrowButtonSelectedThemeImageTopMargin"=dword:00000000
"ScrollBarUpArrowButtonThemeImage"=""
"ScrollBarUpArrowButtonThemeImageBottomMargin"=dword:00000000
"ScrollBarUpArrowButtonThemeImageLeftMargin"=dword:00000000
"ScrollBarUpArrowButtonThemeImageRightMargin"=dword:00000000
"ScrollBarUpArrowButtonThemeImageTiled"=dword:00000000
"ScrollBarUpArrowButtonThemeImageTopMargin"=dword:00000000
I'm sure there is a genius in here that could turn this into a cab. Otherwise, copy the text save in a text file add "Windows Registry Editor Version 5.00" as the first line of the text file.
Rename as a .reg file. Import with your preferred reg tool.
In recent posts I've been berated for my efforts to help. I'm no genius, but I have tried this and it's working on my o2 device.
BACKUP BEFORE TRYING. EITHER THE REG ENTRIES OR THE ENTIRE DEVICE
Hope this helps someone
remove .txt from the attached file.
BIG Thanks to johncmolyneux for the cab.
It doesn't work for me. I changed the theme to one of the other pre-installed ones and set the registry values as described above, but there was no change (after a soft reset).
I have made a cab file, but I'm not gonna upload it till we know why it didn't work and I've fixed it.
Did you import all of the values or change a few?
I tried the change a few initially and all I got was the original original (i.e.wm5) scrollbar.
When I imported the file in the first post it worked. These were the only changes that I'd made.
Do you have the original ROM?
The Pop out images are in the windows directory named "01THUMBxxx"
Neville.Holland said:
Did you import all of the values or change a few?
I tried the change a few initially and all I got was the original original (i.e.wm5) scrollbar.
When I imported the file in the first post it worked. These were the only changes that I'd made.
Click to expand...
Click to collapse
The Dusk theme isn't one of the pre-installed themes is it? Did you try it with one of them?
I didn't..... I only used the HTCBlack theme (Which I think it set by default).
I therefore also don't know if the Pop Out Bar is present in the other themes.
I'm going to do a backup and try another theme.
Confirmed working on the DVF Green Theme
Confirmed working on the Classic Blue Theme
Works perfectly, thanks!
There's a lot of misplaced spaces in what you posted, after removing them, it works.
Nvm: comment removed.
That's how it pasted. they shouldn't be present in the txt file.
Neville.Holland said:
Confirmed working on the DVF Green Theme
Confirmed working on the Classic Blue Theme
Click to expand...
Click to collapse
Okay - I'll recheck the cab file then. It must be doing something wrong.
johncmolyneux said:
Okay - I'll recheck the cab file then. It must be doing something wrong.
Click to expand...
Click to collapse
Did you do it from the text file or copied from the screen... reference freyberry's comment...
Neville.Holland said:
Did you do it from the text file or copied from the screen... reference freyberry's comment...
Click to expand...
Click to collapse
I just read it from the screen - it's the simplest way to then recreate the structure in Visual Studio. I've already had spaces in my posts before now, so I was aware of that issue.
Anyway, I've fixed the cab file and it works a treat now, so I'll send you a link to it so you can download it and attach it to the 1st post, rather than have it here on the second page.
The Cab?
Could you you create a cab or still having error?
johncmolyneux said:
I just read it from the screen - it's the simplest way to then recreate the structure in Visual Studio. I've already had spaces in my posts before now, so I was aware of that issue.
Anyway, I've fixed the cab file and it works a treat now, so I'll send you a link to it so you can download it and attach it to the 1st post, rather than have it here on the second page.
Click to expand...
Click to collapse
gsidhom said:
Could you you create a cab or still having error?
Click to expand...
Click to collapse
I've created the cab, uploaded it and sent a link to Neville.Holland so he can post it in the first post, rather than have it in the middle of the thread.
But I guess since people may want it straight away (and he's not currently online), I can post it here and just remove it when he does his thing later.
Thank You For Effort
Thank you very Much,
By the way I'm Still An HD User But I will Try it on mine
johncmolyneux said:
I've created the cab, uploaded it and sent a link to Neville.Holland so he can post it in the first post, rather than have it in the middle of the thread.
But I guess since people may want it straight away (and he's not currently online), I can post it here and just remove it when he does his thing later.
Click to expand...
Click to collapse
gsidhom said:
Thank you very Much,
By the way I'm Still An HD User But I will Try it on mine
Click to expand...
Click to collapse
I think this is a windows 6.5 thing, so if you're still on 6.1 it probably won't do anything, but I'd be interested to know what happens
Prted HD2 Rom
I 'm Working on Wm6.5 Ported Hd2 with manila 1921,
But Yet It didn't work,
I don't know why: Probably the images files for the popup button aren't included...
johncmolyneux said:
I think this is a windows 6.5 thing, so if you're still on 6.1 it probably won't do anything, but I'd be interested to know what happens
Click to expand...
Click to collapse
gsidhom said:
I 'm Working on Wm6.5 Ported Hd2 with manila 1921,
But Yet It didn't work,
I don't know why: Probably the images files for the popup button aren't included...
Click to expand...
Click to collapse
Check the windows folder for a series of images starting 01Thumbxxx. I suspect that it's a little more in-depth than a few images.
gsidhom said:
I 'm Working on Wm6.5 Ported Hd2 with manila 1921,
But Yet It didn't work,
I don't know why: Probably the images files for the popup button aren't included...
Click to expand...
Click to collapse
That can soon be fixed
Edit:
The second one is there - it's just a bit hard to see
Thanks for the .cab, johncmolyneux!
Hope you don't mind if I add it to the add ons for my ROM?
I hope someone of you could help me! I'm cooking roms for xperia X1 with last EVK on windows XP!
I'm now using build 23568 or 23569 and a strange thing is occurring:
I've cooked successfully a pair of rom and then I needed to change something.... after that all my roms with that builds suffer by strange trouble:
when selecting a ringtone for the incoming call (I can preview its sound) and then hit OK to confirm it all the ringtones roll up and down for a second on the screen and then the default ring (windows-phone) is autoselected and no chance to close that window....... so I can't select different ringtones.
I've tried to revert back the change I made but the same happens. If I try to cook an older build I have in EVK it's working fine!!! I've tried to completely remove 23569 build and put it on from beginning but the same thing happens.....
Please help me! This is driving me crazy!!! I've searched up and down on this and other forum but nobody seems had this issue before.....
Does windows media player work? If it doesn't then it's a XIP issue: make sure you used the latest msxipkernel package.
I had that issue twice long ago. One time is was xip issue, the other time a bad lockstreamdrm package
Thanks a lot for the help! It was a xip issue..... I don't know why the msxipkernel had been modified.... restored the original one and it works!!
Thanks again.
Another XIP-file case solved!
I am having this exact same problem.....
i replaced the XIP and lockstreamdrm on first boot i was able to go into phone options and hear the ring tone without the corrupt error... but after just a bit i get a phone call and its silent....
i go back to phone options and try to play the ringtone and get the corrupt error...
After that i was doing some bmp replacements within the phcanimages and phcanimages2 and after replacing those to dll's on my device (they were the same as the ones cooked in, just updated bmps) i can choose ringtone without error and it rings on incoming calls...
any ideas?
did a clear storage and when phone came up i was able to select ringtone without error... was not able to try a call then because i had to activate phone..
after soft reset i am able to choose and hear when call is coming in..
so maybe the clear storage did it? i will report back after cooking again
This is most likely due to using the Lockstream DRM packages in EXT without the corresponding registry entries at the bottom of boot.rgu. Don't ask me why they put reg. entries from one program in two different places.
jwzg said:
This is most likely due to using the Lockstream DRM packages in EXT without the corresponding registry entries at the bottom of boot.rgu. Don't ask me why they put reg. entries from one program in two different places.
Click to expand...
Click to collapse
How can i fix?
after a few hours of ringtones working fine, i tried to go back into ringers and get the same corrupt error.......
Delete the Lockstream DRM packages (NOT Lockscreen) out of your ROM and see if it works normal.
jwzg said:
Delete the Lockstream DRM packages (NOT Lockscreen) out of your ROM and see if it works normal.
Click to expand...
Click to collapse
gotcha
trying now
I removed the Lockstream DRM packages from my kitchen recooked and still same error...
i also put fresh SYS & XIP's into kitchen...
im using the same kitchen i always have and didnt change anything that i havent changed before.... been cooking my BigMaxsense ROM for months now without this problem..
Thanks for any help
Okay just wanted to post what was causing my problem
i stripped my ROM clean and only put the essentials into it and started adding things a few at a time..(guess i should have done this to start with)
found out that Microsoft.Voice.Command.v1.6.21725 was the root of the problem.. removed it and everything works fine..
thanks to all that helped!
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...
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.
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.