hello everyone!
im using schaps version 4.30 right now. having low sound problem. from my understanding theres a forum tells you how to raise the sound up louder from registry editor but i forgot where. so please can someone help me.
Thanks!
are you having the same problem as me?
my problems are posted here
hope some of my suggestions can help yours
Low phone volume when using Schap's roms
I had the same problem when I use any of Schap's roms. I solved it by changing Schap's roms before flashing it.
Things I change:
1. Changed the attributes of all SetAcoustic*.* files so that these files are no longer hidden.
2. Added the command to config.txt (or preconfig.txt, depending on what rom of Schap your using) to launch SetAcoustic at initial startup.
As a result the SetAcoustic programs runs for a long time (at least for more then a minute) changing a lot of volume settings. From then on I'm able to raise the volume of my phone when I'm in a call to a level that even people close to me can hear what the caller says without using the speakerphone.
Kind regards,
Jos.
After reading yoru post, i've been trying to do what you did, but i have no idea how to extract nb files.
Could you post the step by step instructions on how to alter Schap's roms? would love to try and see if that fixes my long term problem
Low Sound Problem - Solved
List everything you need to do to change a ROM to include SetAcousticParam is to much work.
Instead I've uploaded the modified rom of Schap's WWE 4.30.
You can find it here.
Have fun.
Kind regards,
Jos.
I just poweroff my Jasjam for few minutes and poweron after. then I must raise the volume of my phone.
jgeerts said:
List everything you need to do to change a ROM to include SetAcousticParam is to much work.
Instead I've uploaded the modified rom of Schap's WWE 4.30.
You can find it here.
Have fun.
Kind regards,
Jos.
Click to expand...
Click to collapse
File is temporarily unavailable.... but thnxs anyway...
Hi, everyone! I´m still working on a Wizard (don´t want to touch my Hermes, yet). I´m pretty advanced... but
I dump the [latest] original cingular WM5. I rebuilt it with office 2007 and realize that the original shortcuts are still there. Of course, they are both useless (as I have new names for the apps) and annoying (because I can´t remove them before compiling).
This is the whole point: Those shortcuts are not coming from neither an xml update for the XIP nor an initflashfiles.txt
HOW ON EARTH DO I REMOVE THEM. I can´t find what is creating and copying those shortcuts
Are they embedded in the OS.nb file? If so, how do I take that file apart?
Any help is very much appreciated!
..provxml, m8..
Nope, had checked already
*.mopvxml, etc had been checked.
But... what did you mean by m8?.
BTW: I will check inside os.nb now, but please give me fresh ideas
You may also want to check for a file called initflashfiles.dat. That contains a lot of shortcut information as well. Especially for apps that are default for that particular ROM. It should be found in the OEM\OEM_LANG_* folder in the kitchen. The (*) is the locale number. For example, a WWE ROM would have the folder as OEM_LANG_0409.
Yep, solved (initflashfiles.dat)
Hey, thanks! You´re FAST!
I was about to post it. But thanks, you could have saved me hours
Anyways. If anyone ever reads this thread, remember: scavenging os.nb(a) isn´t that great. An automated kitchen does it all (Hypercore in this case).
I also found somebody claiming that certain shortcut came from a dll. Just keep as a sidenote.
Cheers!
I've been reading an gathering information for weeks now to build my own personal ROM. Since I'm unable (at the moment) to build one from scratch
Somehow it doesn't seem to work for me and I could not find an answer to my problems. I really hope some ROM Guru is willingly to help me out here.
I've used the Diamond Kitchen to extract the NBH files. And like it should it creates the OEM and SYS folders when you don't use protected ROM's like Dutty's, Swtos or Bepe's.
I've tried multiple ROM's to rebuild for my personal needs. And here are the most common problems I've encountered:
- Diamond (or Raphael) Volume Control does work. Even when it's included correct in the ROM. Reinstalling Volume Control after flasing using a CAB does work strange enough.
- The sound settings panel won't close after changing sounds.
ROM's I've tried to personalize:
- Panosha
- TOR (SubZero)
- SwiftBL
- VIC Lite
- And probably a few other ROM's I managed to extract (using the kitchen).
I've read some threads about the same problems but they seem to be part of a ROM thread instead of a specific "cooking thread". That's why I started it here.
Do you experience the same problems or do you have some good ideas than please let the rest of us know
I have the same problem
Everything seems OK, except the damned sound configuration.
If someone has an answer, we would appreciate it very much.
Thanks in advance...
Thanks for you reaction. Concerning the Volume Control, there is a way to get this to work. Just add a CAB that you call using the config.txt.
It's not ideal but it should work.
Unfortunately this procedure can't be repeated for the sound setting panel
I played with it a lot and even if I do nothing with the ROM, this sound config problem occurs. I extract the ROM and then rebuild it without modifying anything. This looks like a kitchen problem I thought.
I use Surface Kitchen v1.01. You another one, so this is a little confusing
Edit:
Maybe we can do the same without using those settings but direct in the registry?
Someone knows those keys?
Been using Kitchen 1.0.1 for a couple of days now as well. Updated the programs that were out of date. Did not help.
I also get always this error, could it be the cause?
iXiR said:
I also get always this error, could it be the cause?
Click to expand...
Click to collapse
HI iXiR
I also get the same error every time. I can not even cook the packages made with package creator. Some times I succeed but at the end it saye User.hv / custom.hv not found. Any idea?
thanks
tararura said:
HI iXiR
I also get the same error every time. I can not even cook the packages made with package creator. Some times I succeed but at the end it saye User.hv / custom.hv not found. Any idea?
thanks
Click to expand...
Click to collapse
Well, most of the times this fault is there, its a mistake with your new or edited rgu file like \\ or forgotten empty last row.
regards
Anja31
I recommend you guys try cooking the 1.93 official ROM .., i cooked a personal one for me .. no problems at all
iXiR said:
I also get always this error, could it be the cause?
Click to expand...
Click to collapse
this error is because you also have xip directory already listed in ur kitchen, so when the operation reaches that part of extracting the xip it dumps the xip and .dsm a.rgus, so basically a duplicate I dont use this kitchen but you can always press y to overite all
- The sound settings panel won't close after changing sounds.
Click to expand...
Click to collapse
Try adding this one to your registery:
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\LSOMACORE]
"Dll"="LsOmaCore.dll"
"Prefix"="DRM"
"Index"=dword:00000001
reset and you will be able to change the ringtone/press ok on your sound settings
To make it work while cooking, just place this in a RGU file so it will be implemented in the ROM
Thanks will try that one as soon as I can.
Had one crazy thought. Since there are some replies from some real cookers here I was wondering about the next thing.
At the moment I always select option "1" in my kitchen. So I don't rebuild it (option "2"). It shouldn't but is it possible to have more success when using option "2"?
I tried all variants....
select 1 (yes) -> Access denied
select 2 (no) -> the message will appear for a lot of files... even when you always select 2 the ringtone panel won´t work
select 3 (all) -> access denied
So IMO it has no impact, which option you take...
I choose "1". I just want to cook the ROM.
Ah.. now I understand what you mean... the question at the beginning...
of course you have to select "1"...
I talked about the overwriting question (screenshots in post before)
First of all: thanks for this thread...I was going crazy with this issue..!
Has anyone tryied the reg.key posted before?
PS: @maccune...did you tryied to recook swiftbl?! How?! Is it not a protected rom??
Might be wrong about SwiftBL. Tried so many that I could be mixing them up
Tried so many because I hoped there would be one that would work just fine.
If it was up to me I'd use TOR v5 since it's basic and still a Diamond build.
Also the cooker told he didn't mind if people would use his ROM as a base ROM for your kitchen
duttythroy said:
this error is because you also have xip directory already listed in ur kitchen, so when the operation reaches that part of extracting the xip it dumps the xip and .dsm a.rgus, so basically a duplicate I dont use this kitchen but you can always press y to overite all
Click to expand...
Click to collapse
Hi dutty, what do you use to cook and protect your rom ? a made home version ?
Sorry, wrong thread...
Caspertje19 said:
Try adding this one to your registery:
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\LSOMACORE]
"Dll"="LsOmaCore.dll"
"Prefix"="DRM"
"Index"=dword:00000001
reset and you will be able to change the ringtone/press ok on your sound settings
To make it work while cooking, just place this in a RGU file so it will be implemented in the ROM
Click to expand...
Click to collapse
Wohoooooooo!
It works... really great... perfect...
I also was going crazy to this issue....
now its solved.....
thx a lot.....
BUT: Another question: How can I add this as RGU File to ROM?
guys,
i been trying to get help for a predictive text problem i'm having since i installed pdaviet manilla2d v18 on my hermes. it comes with those diamond keypads and predictive text for enu/esp/fra/ger/ita but not for portuguese (??????)
this rom is special cause it managed to get manilla2d working fine on hermes and still letting me do everything else, without compromising much speed. it's a found and i want to keep it until i find something better.
this rom won't let me install this cab HTC EzInput QVGA FullKbd 0409-RC1.cab which contains the same keypads but with various language packs. it will end up with the insufficient system permissions message. i did get it working on the V19 but this rom version is so buggy i had to step back to V18. I have also tried installing separate language packs but they won't work.
this insufficient system permissions problem has been covered before in this forum but has not been resolved as the one who had the problem found a different cab to use.
the only ways i see for fixing this would be get rid of security - which i've already tried using a microsoft program that keeps querying device for ever and ever and won't let me change anything or maybe finding another similar keypad kit with language packs that won't bump into the security level of this rom.
chef has released V20, will try this too in the mean time.
Check if you have .net 3.5 installed on your Hermes. I find it missing a lot. Re-installing might work too...
ultramag69 said:
Check if you have .net 3.5 installed on your Hermes. I find it missing a lot. Re-installing might work too...
Click to expand...
Click to collapse
I do, yes. This is one of the first things I install after a flash, without it I can't run AdvConfig... have considered that too.
Well.
Now I am laughing at how obvious it was.
I thought: what is the most common cause of screen not reacting on touch?
And the answer immediately came to me: touch.dll
I am russian and I am cooking my own ROMs. I use native 6.5 kernel and special OEMDrivers from the thread about it. And since I started using them I had the lockscreen bug.
So I dumped official RUS ROM v.2.03 and took touch.dll from OEMDrivers. Then I used Total Commander to copy it to Windows directory. Soft Reset and voila! No bug!
I haven't tried to put it in OEM and cook a ROM (maybe recmod will corrupt smth, don't know - not a specialist), but I think that the whole recipe is: take any OEMDrivers you like, then replace some of them with those from native kernel thread and while doing it DO NOT REPLACE touch.dll.
WARNING: it is presented as module in native OEMDrivers pack, so look for the folder touch.dll and delete it.
Link to native kernel thread: http://forum.xda-developers.com/showthread.php?t=546174&highlight=native+kernel
EDIT: Confirmed that cooking that way will help you to get rid of the lockscreen bug .