Database Develop

[SOLVED] CameraRunner.exe not found (Problem caused by osKitchen alpha)

I've been trying to build my own ROM using osKitchen. Everything has worked and I've been able to upgrade a stock ROM to build 23569. The only problems I've had are with the panel and camera software. The panel and camera buttons on my phone don't work. Pressing either of them will give me an error that the program that should be launched can't be found. CameraRunner.exe is in the Windows folder. I am able to launch it but none of the icons for the UI and menus appear. I am still able to take pictures.
PanelManager.exe is different. When I run that I'm presented with a black screen. I am unable to do anything to close it. It hijacks the Today screen. Other than that the phone will still work normally.
I assumed that these problems were caused by changes I made to the ROM but that doesn't appear to be the case. I imported my stock ROM into osKitchen and built it without changing anything. The resulting ROM had the same issues.
I searched the forums but could not find a solution to this problem. Does anyone know how to fix this? Thanks in advance.

For CameraRunner.exe, did you include the Xperia camera package?
For the Panels, you probably excluded one or more packages needed for this to run proper.

try this camera package

Lokatho said:
For CameraRunner.exe, did you include the Xperia camera package?
For the Panels, you probably excluded one or more packages needed for this to run proper.
Click to expand...
Click to collapse
I initially thought that might be the case but I tried building the ROM with all original packages included and without any modifications and it still has this issue.
spikegotti said:
try this camera package
Click to expand...
Click to collapse
The package didn't help. Pressing the camera button gives me an error and the icons are still missing if I run CameraRunner.exe manually.

I was using OSKitchen too, having troubles(Not sure how to get it to the next rom or w/e) anyway to get camera to work, I used the X2 Camera Update as a package Use the Package Converter option up the top > choose cab > choose the camera > tick it > build ROM > Install ROM > Camera should work
Also my panel manager didnt work through OSKitchen either.

I figured out the problem. The alpha version of osKitchen doesn't copy the PROVXML files into the ROM, which means that the files for the camera and panel software won't be moved to their correct locations. The old version, 1.30v3, doesn't have this problem. The camera and panels work in the ROMs I've built using that version.

glad you could work it our
can you pls change thread title, like add [SOLVED] and rephrase to better describe the content?
thx a lot, appreciate your help

I added [SOLVED] to the title of the thread but I don't understand what you want me to rephrase.

hey, I meant it like this: you don't have problems with the file in one of the custom roms available here (with the need to just reinstall it) but while trying to cook your own and the problem was kitchen (oskitchen, alpha) related, so it would be nice to have that in the thread title to clarify the content and that it's dev related, nothing more, just a suggestion
thx and best

1. Kernel and 2. Rom Error Questions

I tried to word the title correctly to establish that I want to ask 2 different questions, but dont want to clutter up the board with 2 separate posts
Please help if you can
1. Kernel
Why do some kernels work with some roms and not others? I have taken a Sprint Rom, ran it through the kitchen, and tried flashing any number of kernels. The only one that works is Zenulators AnyKernel. I know at times only the stock overclocked worked, but I think at certain times I have gotten the no perf lock to work (though that may have been with an NFX Rom, and not one that I created myself). This leads me to ask why would a kernel work for a rom that is built from the same base that I am using, but not on mine? Is dsixda's kitchen not the one everyone uses? I just dont understand why I am limited to one kernel that is not undervolted and overclocked. I would like to put a 768 overclocked, undervolted kernel with this rom, but cant get any to flash. Should I just use the kitchen to "port" the kernel. How does nfinitefx45 get the kernels he posts to work with a Sprint base? Is the kernel edited in some way? Im not calling anyone out, just trying to learn how to get a good kernel to work with my rom.
2. MAJOR issue: when running df, I get an error that etc/mtab: no such file or directory. What I have done is in the paragraph below
I decided to take another cracked at a minimal Sprint 2.1 Rom. I used dsixda kitchen 0.107 to root, add busybox, remove boot sounds, deodex, add data/app, add nano + sysrw, sysro, bash, and zipalign the .7 Rom. I then removed all Sprint apps except for VVM, all google apps, all htc apps and widgets that were not explicity needed (need the contacts and ime apks among a few others), removed a ton of system apps (can provide a list of current system/app dir and a list of all that was removed if it will help). I edited the lockscreen so it wasnt in landscape mode all the time. Added an OMADM.apk file that didnt FC when I tried to update the prl (tested the update and it works). I did find an EPST.apk that adds ## codes back to the dialer (should I include that in the rom...wasnt intending on it as the only ## code that doesnt work is the prl...data works) OMADM.apk is smaller that the EPST...but EPST does exist already...and I might be able to pull OMADM meaning 0 firmware, profile, or prl updates...but you could do ##prl manual...I dont know, still thinking it through. I did end up creating a google apps zip file with the apps from the .7 rom so that market will work (removed maps as it wasnt up to date and the Streets.apk never worked, but left gmail, youtube, voice search to work with jonasl's htc keyboard, and of course gtalk). In doing this, I am thinking about creating some packs for the rom, but really need the above 2 questions answered to find out where to go from here.

evilvoice said:
1. Why do some kernels work with some roms and not others?
2. MAJOR issue: when running df, I get an error that etc/mtab: no such file or directory. What I have done is in the paragraph below
Click to expand...
Click to collapse
afaict, the 'kernels' are literally just the linux kernel that provides some basics to the os... altho linux IS a monolithic kernel, it is not a bsd-system that has all the tools completely-compiled for the system together...
thus, the answer to 2. is that you have deleted too much of the periphery, for instance the actual mount-table system that df uses to to check... (ie: some prog creates the mtab, and apparently it is not the kernel, i guess)
alternatively, the answer to 1. is that there is actually too much in the roms that are using something unique to each kernel that you are trying to install (altho that seems odd to me)... thus, the only way that the rom will work is if you give it the kernel with the tools that it (the rom) needs...
tbh - im not exactly sure - ive not gone into the depths of kernel-swapping that youre trying to explore... in full-linux-systems, the kernel is fairly easy to update without breaking all of the miscellaneous tools - however apparently the android-roms are more tied-together than a normal linux system...
gl and maybe someone with more experience will give an accurate (rather than a guessing) answer...

Move Sense apps to SD

Hi Evryone,
I have tried OldWildPuzzled (with remove HTC sense script) and like the speed and simplicity.
Now I'm trying SUnAaBh ROM and I've been manually removing sense app to try to speed up the ROM.
The question is, I do like some of the HTC apps (but hate many of them) and would like to keep them behave just like any other downloaded apps. Stay in SD and load it up when I wanna use it.
Is this possible? What kind of procedures I should do to the system to acheive this?

[Q] Contact restore V1 to V2.3.4

Just flashed CM7 the other night. Things working flawless, but trying to restore contacts v1 into CM7 from TB backup does not seem to work. Is the internal contact structure seriously changed.
Anyone have any suggestions other than flashing back to something else and use a different tool to export internal contacts?

doctor_r said:
Just flashed CM7 the other night. Things working flawless, but trying to restore contacts v1 into CM7 from TB backup does not seem to work. Is the internal contact structure seriously changed.
Anyone have any suggestions other than flashing back to something else and use a different tool to export internal contacts?
Click to expand...
Click to collapse
Please ask all rom related Questions in their Q&A threads instead of opening a new one. It is always better to use a contact backup app or the built in optin in the contacts app then trying to sayd database files. Things due change and if enough of a change takes place then you wont be able to use the db file.

[Q] getting stock rom swype on cm7.2

Hi,
I found a topic which helped people to get their original stock rom swype back in their custom rom.
I tried the same but it didn't work for me. One part of the process is checking in build.prop that the ro.product.brand is the same in the original stock rom and in the custom rom. Which is so for my custom rom and the stock rom i've downloaded.
However, I saw that the build.prop from the stock rom uses GT-S5830 as type for the other lines like:
ro.product.model=GT-S5830
ro.product.name=GT-S5830
ro.product.device=GT-S5830
ro.product.board=GT-S5830
and that my custom rom has cooper there instead of GT-S5830. I added the lines above to my build.prop, hoping that this would solve the issue.
Unfortenately, it doesn't. When I select swype, there's no language available. I've checked in the apk file and alle the language files are there so it seems that swype blocks usage of it.
When I select swype, I get this message:
"the swype package you installed is configured for another device and will operate with limited functionality."
I'm using cm 7.2. the ultimate and extracted swype from this sammobile stock rom:
S5830XWKTQ_S5830VITKT2_S5830XWKT8_HOME
Can someone tell me/help me with isolating the problem? Why does swype still not recognise my device as GT-S5830?

DutchArjo said:
Hi,
I found a topic which helped people to get their original stock rom swype back in their custom rom.
I tried the same but it didn't work for me. One part of the process is checking in build.prop that the ro.product.brand is the same in the original stock rom and in the custom rom. Which is so for my custom rom and the stock rom i've downloaded.
However, I saw that the build.prop from the stock rom uses GT-S5830 as type for the other lines like:
ro.product.model=GT-S5830
ro.product.name=GT-S5830
ro.product.device=GT-S5830
ro.product.board=GT-S5830
and that my custom rom has cooper there instead of GT-S5830. I added the lines above to my build.prop, hoping that this would solve the issue.
Unfortenately, it doesn't. When I select swype, there's no language available. I've checked in the apk file and alle the language files are there so it seems that swype blocks usage of it.
When I select swype, I get this message:
"the swype package you installed is configured for another device and will operate with limited functionality."
I'm using cm 7.2. the ultimate and extracted swype from this sammobile stock rom:
S5830XWKTQ_S5830VITKT2_S5830XWKT8_HOME
Can someone tell me/help me with isolating the problem? Why does swype still not recognise my device as GT-S5830?
Click to expand...
Click to collapse
www.swype.com/
Install it from Google Play Store, you also can try Swiftkey

Viper The Ripper said:
www.swype.com/
Install it from Google Play Store, you also can try Swiftkey
Click to expand...
Click to collapse
installing from google play (or even amazon app store) would be an option when they would add PayPal support to pay for the app.
As long as I need to have a credit card, I cannot buy anything from Google Play or Amazon App store.
Therefore, I am hoping there is a solution for the difference in the build.prop file...
perhaps to include it in the zip file from the custom rom, but Im affraid the problem persists as the build.prop is still different.
I still hope the builde of this rom can send me his stock swype and libswypecore.so files...
Or is there another solution for this? (adjusting build.prop and inserting the lines with GT-S5830 was not one)