Hello everyone,
I want to start this thread so we can discuss ways to improve the pathetic camera software that comes bundled with Windows Mobile 5.0.
I'm tweaking the Registry and I found several interesting things, but for the time being, I have only managed to enable/disable the camera shutter sound (or even change it to some other sound).
With your favorite Registry Editor, navigate to HKLM/System/Pictures/OEM and change the ShutterSoundVolume value from 32768 to 0
Save changes and test camera. If you like the results power down the Pocket PC, wait 2 secs then Soft Reset with stylus.
That's it!
I will be posting some more findings as they become available.
My goal is to improve the capture quality of the Video Capture portion of the application.
Best regards,
Rayan
Now that's the greatest thing i've ever heard ... We need to fix the camera because its quality is really bad.
Now let's see . IA camera is 100 times better than the one installed on the device ( v2.10 ) . After installing it , the Album works fine BUT when running the camera application , i have nothing but a black screen :evil:
Now maybe we can do something to disable the installed one and use the IA instead.. i think it would be gr8 :idea: :twisted: :twisted: :twisted:
nice thread thanks for adding this topic in the wiki .. but i move the thread to Himalaya Upgrading etc. to avoid confusion with other HTC devices ..
anyway heres my input ..
the exact commandline to call the camera is
pimg.exe -camerakey
icon is found in shellres.dll to be exact -8263(shellres.dll,-8263)
user Settings can be found in this registry Section
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Pictures\Camera\USER
AudioEnabled--> 1 to Enabled, 0 if not
Brightness--> Set to the Following value
dword:00000000 --> +3
dword:00000001 --> +2
dword:00000002 --> +1
dword:00000003 --> 0
dword:00000004 --> -1
dword:00000005 --> -2
dword:00000006 --> -3
Resolution --> Setting Picture Resolution to the Following Value
dword:00000000 --> 240x180
dword:00000001 --> 480x360
dword:00000002 --> 240x360
dword:00000003 --> 480x640
CurrentZoom --> this doesnt work with mine but hope to you guys
dword:00000000 --> Zoom *1
dword:00000001 --> Zoom *2
dword:00000002 --> Zoom *3
dword:00000003 --> Zoom *4
dword:00000004 --> Zoom *5
dword:00000005 --> Zoom *6
Save Files to:
Main Memory(Default)
"DefaultDir"="\My Documents\My Pictures"
"DiskName"=""
FOLLOWING Will Create DCIM Folder
Extended_ROM
"DefaultDir"="\Extended_ROM"
"DiskName"="DSK1:"
NAND Disk(Storage)
"DefaultDir"="\NAND Disk" or "\Storage"
"DiskName"="DSK2:"
Storage Card
"DefaultDir"="\Sotrage Card"
"DiskName"="DSK3:"
to any Other Folder
"DefaultDir" --> Set the Folder path ex. "\Program Files"
"DiskName" --> Set to what disk
(Empty) --> Means in your device(RAM)
DISK1: --> Means Folder in Extended ROM
DISK2: --> Means Folder in NAND Disk or Storage
DISK3: --> means folder in Storage Card
File Number and File Prefix
"FileNumber" --> Setting the File Number Current Count
"FilePrefix" --> File Prefix for Picture
Setting The Video Resolution
VideoProfile
dword:00000000 --> PC(240x180)
dword:00000001 --> PC(128x96)
dword:00000002 --> MMS(162x120) <--Dont Ask y its wmv
dword:00000003 --> MMS(176x144)
Setting Time Limit For Video
UserVideoTime --> value must be in seconds default is 1Ehex(30 in decimal) means 30second
QualitySetting --> Setting Quality Settings
dword:00000000 --> High Quality
dword:00000001 --> Normal Quality
dword:00000002 --> Low Quality
Camera Driver can be found in the Following Registry Section(pls study this)
HKLM\Drivers\BuiltIn\Camera
and
HKLM\Drivers\BuiltIn\CameraDriver
To Disable the MS Camera
Remove the Registry Key "Capture" in this Registry section
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DirectX\DirectShow]
or Simpy Remove the Value of DLL which is "CameraDriver.dll" in this registry
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DirectX\DirectShow\Capture]
THANKS AGAIN RAYAN FOR ADDING THIS TOPIC IN THE WIKI .. FEEL FREE TO EDIT THE WIKI .. :wink:
Thank you toenailed for the detailed description of the registry...
This will save us some time.
Let's see what we can do...
Best regards,
Rayan
minor correction
NOTE:
The correct path to the Camera Key in the Registry is:
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Pictures\Camera\USER
But thanks again toenailed! :wink:
oooppps sowee thanks rayan .. just edited my post .. :wink:
Does this mean that by disabling the MS camera, we can use IA Camera instead?
I hope so 8)
Solved "slow" camera response problem???
I have accidentally solved the slow camera problem in my Hima but, unluckily I don't know which of the programs or drivers I installed did it!?
I maybe able to simulate it if I do a soft reset once again but it will be another tedious job of reinstalling the apps one-by-one, since I'm now using Sunnysoft Backup Manager to do away with the tedious reinstallation process.
Can anybody with slow camera problem pls try if the attached file [CameraRC10_Streaming_reg.CAB] solves the problem?
I will appreciate a feedback on the matter so that on my next soft reset I don't have to sort out the apps or drivers to test which one solved it!
Thanks a lot.
Re: Solved "slow" camera response problem???
rhmartin said:
I have accidentally solved the slow camera problem in my Hima but, unluckily I don't know which of the programs or drivers I installed did it!?
I maybe able to simulate it if I do a soft reset once again but it will be another tedious job of reinstalling the apps one-by-one, since I'm now using Sunnysoft Backup Manager to do away with the tedious reinstallation process.
Can anybody with slow camera problem pls try if the attached file [CameraRC10_Streaming_reg.CAB] solves the problem?
I will appreciate a feedback on the matter so that on my next soft reset I don't have to sort out the apps or drivers to test which one solved it!
Thanks a lot.
Click to expand...
Click to collapse
That's good news!!!
I will try it as soon as I get into my office...
Best regards,
Rayan
few flaws in wm 2005
i am using buzz lightyears 2005
which is stable here are few flaws
1. in camera mode it shows the option of zoom
but after clicking on 6 mode nothing happens
2. in phone mode when in conversation , i get the option
of turn hands free on, but after clicking on it nothing happens
have to use it manually by pressing the green button
3. where can i get this halo2 theme which changes the overall
look of the phone
http://forum.xda-developers.com/viewtopic.php?t=21478
Re: few flaws in wm 2005
isk2005 said:
i am using buzz lightyears 2005
which is stable here are few flaws
1. in camera mode it shows the option of zoom
but after clicking on 6 mode nothing happens
2. in phone mode when in conversation , i get the option
of turn hands free on, but after clicking on it nothing happens
have to use it manually by pressing the green button
3. where can i get this halo2 theme which changes the overall
look of the phone
http://forum.xda-developers.com/viewtopic.php?t=21478
Click to expand...
Click to collapse
1. Yes, it appears that the ZOOM does not work yet... Remember that the WM5.0 version we have is not the final version...
2. If you enable Bluetooth and turn on your BT Headset, that option works... Maybe you are talking about the Loudspeaker function.
3. I've been looking all over the place for that Theme. No luck yet.
thanks
thanks for your advice rayan
if u find the theme u know
where to post
Can somebody please extract these dlls from WM2003 or SE and post them here?
aacdll.dll
aygshell.dll
colorconvscaling.dll
coredll.dll
gsmamrdll.dll
gsmamrenc.dll
gx.dll Path
h263videoenc.dll
mfcce300.dll
midilib.dll
mp4_reader.dll
mp4spvd.dll
mp4writer.dll
mpeg4spvideoenc.dll
note_prj.dll
I'm trying to make the old IA camera software work under Magneto.
Thanks!
Rayan
rhmartin wrote:
I have accidentally solved the slow camera problem in my Hima but, unluckily I don't know which of the programs or drivers I installed did it!?
I maybe able to simulate it if I do a soft reset once again but it will be another tedious job of reinstalling the apps one-by-one, since I'm now using Sunnysoft Backup Manager to do away with the tedious reinstallation process.
Can anybody with slow camera problem pls try if the attached file [CameraRC10_Streaming_reg.CAB] solves the problem?
I will appreciate a feedback on the matter so that on my next soft reset I don't have sort out the apps or drivers to test which one solved it!
Thanks a lot.
Click to expand...
Click to collapse
tried it does not help
to ryan about dlls
Nice Idea i'll try to get them from a friend who still has 2003
thanks
Amal
Same here... CameraRC10_Streaming_reg.CAB didn't work at all...
Hey rhmartin, can you give us some feedback on your camera's video performance?
Where you able to reproduce the fix?
Can you post a sample clip?
Thanks!
Rayan
IA CAMERA FOR WM2005
Rayan said:
Can somebody please extract these dlls from WM2003 or SE and post them here?
aacdll.dll
aygshell.dll
colorconvscaling.dll
coredll.dll
gsmamrdll.dll
gsmamrenc.dll
gx.dll Path
h263videoenc.dll
mfcce300.dll
midilib.dll
mp4_reader.dll
mp4spvd.dll
mp4writer.dll
mpeg4spvideoenc.dll
note_prj.dll
I'm trying to make the old IA camera software work under Magneto.
Thanks!
Rayan
Click to expand...
Click to collapse
Hey rayan,
any developments on making IA Camera WORK???
update us please......
Unfortunately there are no news on the front....
I've never received the set of DLLs from WM2003SE that I requested (see above posts)... :?
Without them I can't proceed...
the files is included in Camera and Album cab
but i suggest you to use the Dumped Magician OS since the Album and Camera is much newer than in Himalaya Wm2003SE (camera or album i think is version 2.70 or greater)
i will uploade the Dumped Magician ROM 1.11.00WWE in
ftp://xda:[email protected]/Magician/magician.rar
its size is 15.2MB, so it the file is smaller pls download later till i finish uploading it ..
but if you want to thoroughly study the MS Camera .. study it in this Registry Section
HKEY_LOCAL_MACHINE\Software\Microsoft\Pictures\Camera\OEM
-toe
Rayan said:
Unfortunately there are no news on the front....
I've never received the set of DLLs from WM2003SE that I requested (see above posts)... :?
Without them I can't proceed...
Click to expand...
Click to collapse
WASSSSUUUUPPP!!!! toenailed is GODSENT!!!!
LETS HOPE Rayan works his magic on wm2005 IA CAMERA!!!!!
:roll: :lol: :lol: :lol: 8) 8) 8) :roll:
Modifying the LCD density of your screen will provide HUGE REACTIVITY GAIN to the tablet
We can also tweak Dalvik heapsize for large application
Both are editable using software but they're also properties on the build.prop :
- dalvik.vm.heapsize
- ro.sf.lcd_density
Does editing this properties is enough for the Folio follow or do we have to make much complex operations ?
I there, is this fix already implemented or has to be done manually?!?
I've implemented them using FolioWidget rewriting build.prop.
Not sure the folio take care of it.
But it seems that's is not required by users so i'll wipe them
Sol Ido said:
I've implemented them using FolioWidget rewriting build.prop.
Not sure the folio take care of it.
But it seems that's is not required by users so i'll wipe them
Click to expand...
Click to collapse
I dont understand what u mean.
ps: have u read my pm?
Sol Ido said:
I've implemented them using FolioWidget rewriting build.prop.
Click to expand...
Click to collapse
density of 120 works quite fine here now.. with old market app, there was a problem with 120 but that seems resolved now with new market app..
and yes, somehow screen and browsing seems to work better? or is it just the bigger picture giving a nicer resolution of browsing?
All resolution are good. If you have a lot of items on the screen lower density is best.
But by using something like 180 you get a lot of visibility. Since i've developped a lot of complex widgets, it's my favorite one.
Using a density >120 will get you less data to manage on the screen and you can feel the gain ! i'm using multipicture and a lot of complexes widgets and there's not fillrate lag at all.
I was quite surprised with this benefits.
My purpose is that those options can really feet somes users needs. VM heap tricks like the one you found on cyanogen helps on huge application like PDF readers.
But even after editing those properties on the build.prop they are not taken into account. Maybe because of the previous installation i've done. So i'm looking to better understand how to override android properties.
I'm not sure how android handles non-default values for this property.
You should try with one of these:
120 (low-density)
160 (medium-density, Folio default)
240 (high density)
Depending on how this is handled, setting a density different than that may result in broken applications (depending on how the layouts are coded)
Using the LCD DEnsity application i confirm that all resolution are compatible with the folio
Maybe some application will have a bad behavior ! so we've to be able to change the density
metuskale said:
I there, is this fix already implemented or has to be done manually?!?
Click to expand...
Click to collapse
This is no fix, as there are no real issues with these things. Its only a matter of tweaking the folio to your best personal use. They have to be implemented manually.
Shouldn't the dalvik heapsize fix the sound problem with some avi files?
I'm using the foliomod 1.3d, foliowidget works, but some avi files arn't giving me sound
Hello, could someone tell me how the default value for the heapzize is, please? There is only 16, 24 and 32 to choose, but I read something about 64!? How can I choose this value or get back to default?
Thx
Tom
Edit: solved!
I wanted to use the SB Nation Android app, which is basically a program for reading sports articles.
However, I encountered a problem, which I wrote about to the dev:
I just wanted to alert you to what seems to be a bug in your app.
Basically, I cannot see any text in any of the articles. The
background of the articles is a light gray; pictures and text within
quotes show up (so do comments). However, the main text body does not.
I'm running an HTC Flyer on Honeycomb OS.
Click to expand...
Click to collapse
The dev wrote back:
While we don't have an HTC Flyer to test with, but one thing you could try is to check your device settings for something along the lines of
"hardware acceleration" or "GPU acceleration" and turn this option off.
While these options generally improve UI responsiveness, it's a known bug
for them to wreak havoc on embedded web views. Let me know if that does or doesn't resolve the issue.
Click to expand...
Click to collapse
Is there a way to switch off hardware acceleration to test this issue?
I think the app developer is blowing smoke or smoking blow. There is no user setting to turn off the GPU on any Android device. A properly written app can deal with those settings for example MX player knows which formats can use HW accel and which one's need SW codecs.
If you are running on a rooted ROM, there is a parameter in the system/build.prop file
video.accelerate.hw=1
you can change that to 0 and reboot to see what happens. It will definitely slow other things down though.
Acceleration off
Sir,
how can i switch off the HW acceleration,will be helpfull if anybody teach me how to build custom rom with HW acceleration off for nexus 4.
pls help to to learn from you.
Hello!
I'm using a Mate 20 Pro with workprofile enabled via Miradore MDM. If I enable the Darken interface colors switch, the apps in the private profile are shown as expected, but the apps in the work profile are not switching the color as they should and so there are some fonts invisible for example. I think that there is a system package which is handling the color switch and that package needs to be approved for the workprofile. Does anyone have an idea which package that might be?
Thanks for your help!
I found a way to activate the automatic white balancing of google. (Like on the Pixel 4).
Based and thanks to the guide of droidwin: https://www.droidwin.com/how-to-remove-navigation-bar-gesture-pill-on-non-rooted-pixel-6-pro/
You need the fabricate overlay and Shizuku.
In the overlay app: Add overlay ->Android-System->Add->config_displayWhiteBalanceAvailable set to enabled ->apply / config_displayWhiteBalanceEnabledDefault set to enabled-> apply
Close and save it.
After it enable the overlay. Then it appers in settings->Display an d you can turn it on.
That's all.
Is Automatic White Balancing useful? Does it improve the display?
Droidwin based off XDA thread from Nov 6
Also I have it toggled and if doesn't change wb when forcing different colour hues
https://forum.xda-developers.com/t/...l-and-more-for-non-rooted-pixel-6-pro.4357937
I haven't done a test. Do you know how fast the wb change on the pixel 4? Maybe it's too slow on this device?
Can someone post a picture of what this looks like? Even if it's from the pixel 4 or something. Just would like to see it so I can decided if I should care enough to do this....