Related
Under 'Device Information' on my XDA 2 the 'Flash Size' reads as 32mb. Shouldn't it read 64mb? Just to confirm, can a few of you tell me what your XDA 2 says?
If you could reply a.s.a.p I would appriciate it as I've already requested an RMA, but then thought I should double check with the XDA-Developers community before sending it back.
the flash read 32 meg on my machine too.
The XDA II has a 64Mb ROM. 32Mb is used for 'standard' PPC software and the other half is divided between the on board 'Storage' folder and an area used to hold the Extended ROM components that auto-install after a hard reset.
Search these forums for "ROM Size" & "Extended Rom" for further details, but rest assured you got a 64Mb unit.
I did notice the same thing, i.e. I still use XDA I but on many www ads there has been more or less clear distinction that you can buy either 64MB or 128MB XDA II model, strange for me as XDA II has been using in vast of its advertising campaign selling point of having total 128MB memory :?
regards, monika
A himalaya has:
128 MB RAM
32 MB flash (Memory mapped, internal to the Xscale processor)
32 MB flash in a 'Disk On Chip' (addressed as disk, special drivers)
Most of the latter 32 MB is mounted as "\Storage" (16 MB), "\Extended_ROM" (14.5 MB, hidden mount, sometimes locked for writing) and used for various other things, including the boot-time splash image.
For more general hardware details:
http://wiki.xda-developers.com/wiki/HimalayaHardware
Extended_ROM modifications:
http://forum.xda-developers.com/viewtopic.php?t=5514
please let me understand that items clearly ....
128MB memory means you can move the memory tab in start/settings/system/memory between STORAGE and PROGRAM options from 1 to 127MB or there are some limitations imposed ??
I am still with XDA I and ... I am curious
regards, monika
Memory slider
You can move it, but not below the current utilization.
If your device shows 26 MB in use like mine at the moment, you can obviously not move the slider below 26 MB. It also auto moves when needed, If I put it around 27 MB, it will jump up a little after a short while.
I just leave it as is, has not had any need to move it yet. The only application I have that really needs program memory is TomTom Navigator 2 with a large map loaded (Scandinavia).
Regards
Michael
Re: Memory slider
bodstrup said:
You can move it, but not below the current utilization.
If your device shows 26 MB in use like mine at the moment, you can obviously not move the slider below 26 MB. It also auto moves when needed, If I put it around 27 MB, it will jump up a little after a short while.
I just leave it as is, has not had any need to move it yet. The only application I have that really needs program memory is TomTom Navigator 2 with a large map loaded (Scandinavia).
Regards
Michael
Click to expand...
Click to collapse
REGARDING XDA I
heh, seems like I have asked just a minute very much the same question (also regarding ..... auto fall back memory split) but do you know ... why the tab is automatically moves back when I assign less than let's say 4 - 5MB of memory
REGARDING XDA II
what memory split is possible ??
regards, monika
Memory Slider
Monika, I can move the slider to a position inside the blue band, but a 'saf' distance from the ends.
On my current system with 26 MB Storage and 12,48 MBV Program memory in use, I can move the slider between a storage area of about 41 MB to about 98 MB. If I move beyond these values, the slider will pop back to the middle after a couple of seconds.
I just moved the slider to a position with 92 MB storage and 27 MB Program memory free. I then started TomTom Navigator 2. The slider popped back to the middle after TomTom loaded.
As the text tells, it is a temporarily adjustment, the system will move change the allocation as it sees fit.
Regards
Michael
Re: Memory Slider
bodstrup said:
Monika, I can move the slider to a position inside the blue band, but a 'saf' distance from the ends.
On my current system with 26 MB Storage and 12,48 MBV Program memory in use, I can move the slider between a storage area of about 41 MB to about 98 MB. If I move beyond these values, the slider will pop back to the middle after a couple of seconds.
I just moved the slider to a position with 92 MB storage and 27 MB Program memory free. I then started TomTom Navigator 2. The slider popped back to the middle after TomTom loaded.
As the text tells, it is a temporarily adjustment, the system will move change the allocation as it sees fit.
Regards
Michael
Click to expand...
Click to collapse
that is the answer I have been looking for, thank you very much ... now at least I know what to expect once decide to buy XDA II one fine day
regards, monika
I know the Athena community is small compared to the Kaiser user base and their video driver bounty is over $5,000 now. But we suffer the same video issues: Lack of dedicated driver support for ATI Imageon graphics hardware.
I am putting my hard-earned American dollars where my mouth is by offering $100 to any developer(s) who can remedy this.
The intent of this thread is identical to the one over in the Kaiser forum; the "rules" are the same. Who's with me?
I'll put in: $25 for a driver that would make the general UI faster. $50 for a driver that would make the general UI faster and would be able to run full-hardware support mode in TCPMP and/or CorePlayer.
Would the drivers be similar so that we could piggyback onto their work? If so I would ante up some cash to get 30fps video @ true 640x480 resolution!
I will up the ante by USD 50.00 more if everything in this thread can be produced by whoever that can make the ati driver.
I'm down for $50.00 USD also. Lets keep this going gang, someone out there has to have some kinda know how in doing this.
Will this ATI fix work? It totally did for my Hermes.
http://forum.xda-developers.com/showpost.php?p=1636405&postcount=2
juiceppc said:
Will this ATI fix work? It totally did for my Hermes.
http://forum.xda-developers.com/showpost.php?p=1636405&postcount=2
Click to expand...
Click to collapse
This cab caused my device to freeze at the primary splash screen and forced a hard reset.
eaglesteve said:
This cab caused my device to freeze at the primary splash screen and forced a hard reset.
Click to expand...
Click to collapse
****e! Sorry... Guess it doesn't work. I'll try it on mine when I get it but I'm sure it probably won't work since it was "designed" for the Hermes...
Put me in for another 100. I'm really looking forward to this driver fix, and the new version of Flash Lite.
juiceppc said:
****e! Sorry... Guess it doesn't work. I'll try it on mine when I get it but I'm sure it probably won't work since it was "designed" for the Hermes...
Click to expand...
Click to collapse
No worries mate. Still thank you for the post. I know you're only wanting to help. Cheers.
I'll happily chip in $50 - £25 for this too.
Guys... When I look at my Advantage, EVERY indicator is there that the ATI driver is fully integrated. The HKLM\System\DDraw key is pointing at the ATI driver, the drivers are in \windows and the ATI cfg TXT file is there. This is exactly like my HX4705. I have the US Advantage x7501
Why do you think it *isnt* supported and are now offering cash? If its because of the HTC class action issue, please realize that that is specifically the Qualcomm chipset and, personally, I think Qualcomm is a big piece of that problem. The Advantage is a traditional PXA270+Imageon package that is very well known and understood.
Are people feeling the *driver* isnt there because of TCPMP performance? I really hope not. Picard *acknowledges* and always has that TCPMP and now Core Player are just really not good on the Imageon. He has always blamed ATI and says that now they ARE working with him. You can see the threads at coreplayer.com.
Performance on my HX4705 was horrible as well. I see NO issues on the Advantage from a display performance perspective outside of TCPMP (WMP *always* sucks) Games, scrolling, aspect ratio change, etc are all fine. And I see *clear* evidence that the driver is on the device.
Just look at whats in that "fix" ZIP. Always CHECK before using crap like that. The files are ALREADY there on my Advantage. The config file of course will be different and is a HUGE part of the ATI driver on Win Mobile. Putting a CFG file from a different Imageon down will almost definitely cause you trouble.
Before you offer someone your hard earned cash, please research for yourself how to tell what display driver is being referenced (just look at HKLM\Sytem\DDraw\DeviceEnum and see if it indicated ace_ddi.dll - also look at HKLM\System\GDI\Drivers ), locate the files on your device, learn what those files are and look for the ATI cfg file: atihwtbl0.txt
Here is an ANCIENT thread on the ATI driver on Windows Mobile:
http://forum.brighthand.com/showthread.php?t=207466&page=10
Anything look familiar? On my Advantage at least, the driver is CLEARLY there and loaded.
mlambert890 said:
Guys... When I look at my Advantage, EVERY indicator is there that the ATI driver is fully integrated. The HKLM\System\DDraw key is pointing at the ATI driver, the drivers are in \windows and the ATI cfg TXT file is there. This is exactly like my HX4705. I have the US Advantage x7501
Why do you think it *isnt* supported and are now offering cash? If its because of the HTC class action issue, please realize that that is specifically the Qualcomm chipset and, personally, I think Qualcomm is a big piece of that problem. The Advantage is a traditional PXA270+Imageon package that is very well known and understood.
Are people feeling the *driver* isnt there because of TCPMP performance? I really hope not. Picard *acknowledges* and always has that TCPMP and now Core Player are just really not good on the Imageon. He has always blamed ATI and says that now they ARE working with him. You can see the threads at coreplayer.com.
Performance on my HX4705 was horrible as well. I see NO issues on the Advantage from a display performance perspective outside of TCPMP (WMP *always* sucks) Games, scrolling, aspect ratio change, etc are all fine. And I see *clear* evidence that the driver is on the device.
Just look at whats in that "fix" ZIP. Always CHECK before using crap like that. The files are ALREADY there on my Advantage. The config file of course will be different and is a HUGE part of the ATI driver on Win Mobile. Putting a CFG file from a different Imageon down will almost definitely cause you trouble.
Before you offer someone your hard earned cash, please research for yourself how to tell what display driver is being referenced (just look at HKLM\Sytem\DDraw\DeviceEnum and see if it indicated ace_ddi.dll - also look at HKLM\System\GDI\Drivers ), locate the files on your device, learn what those files are and look for the ATI cfg file: atihwtbl0.txt
Here is an ANCIENT thread on the ATI driver on Windows Mobile:
http://forum.brighthand.com/showthread.php?t=207466&page=10
Anything look familiar? On my Advantage at least, the driver is CLEARLY there and loaded.
Click to expand...
Click to collapse
@mlambert890: Thanks for posting. Iwill happily stand corrected if this is true (and change my sig ). I do see the ATI cfg file on my x7501 but not the reg key you reference. I based my decision to post the bounty on numerous threads complaining about the video performance of the Athena as well ass offline disucssions with other Athena owners. Can anyone else lend any insight?
Weird that you dont have the reg key!
Can you check for me and tell me what you see under:
HKLM\System\DDraw and also HKLM\System\GDI?
Maybe we can make a breakthrough here
Also, do you have access to the TCPMP toture test clip? It was the Matrix Reloaded trailer at 640x480x1.6mbps It used to be freely available from a bunch of places, but now it seems gone.
Im curious what your benchmark results would be on that clip. In TCPMP, what video driver setting are you using?
I have no HKLM, System, Ddraw key at all. I do have Drivers, ATI, Camera in HKLM, System, GDI.
EDIT: I will benchmark the clip if I can get it. If anyone is hosting it, PM me please. Could ATI support be in the x7501 ROM only and not in the others (including derivatives of the HTC OEM ROMs?
Really weird... well, if you're feeling adventurous, you can create the DDRaw key...
Basically, its HKLM\System\DDraw
Under DDraw, another key: DeviceEnum
Under DeviceEnum, another key: ace_ddi.dll
Under ace_ddi.dll I have 3 values:
"Description" , string value, empty
"DesktopFlags", DWORD value, set to 0
"GUID", binary value, set to 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
mlambert890 said:
Really weird... well, if you're feeling adventurous, you can create the DDRaw key...
Basically, its HKLM\System\DDraw
Under DDraw, another key: DeviceEnum
Under DeviceEnum, another key: ace_ddi.dll
Under ace_ddi.dll I have 3 values:
"Description" , string value, empty
"DesktopFlags", DWORD value, set to 0
"GUID", binary value, set to 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Click to expand...
Click to collapse
These are all there already in my Dopod U1000.
Good! Those are indicators that, better or worse, the drivers are there and loading.
Eaglesteve, do you have any specific video problems or is it primarily video playback in TCPMP/CorePlayer? I find that everything is great on the X7501 except TCPMP/CP, but I was used to that from my HX4705
mlambert890 said:
Good! Those are indicators that, better or worse, the drivers are there and loading.
Eaglesteve, do you have any specific video problems or is it primarily video playback in TCPMP/CorePlayer? I find that everything is great on the X7501 except TCPMP/CP, but I was used to that from my HX4705
Click to expand...
Click to collapse
I've never found there to be any problem with playing video. All my videos play very smoothly, even those which did'nt run at 100%. As long as I don't do the benchmark, I don't even know that it's below 100%
I had said all along that there are many things to improve in Athena, but Video is not on my list. I played "the dog" video smoothly although others are seeing the slide-show effect. In both cases, the speed are quite the same. The effects are completely different. What that tells me is that benchmark speed may not be a good indication of smoothness. What I see with my own eyes is the only thing that matters.
errrrr....
I dont know what people are expecting. I upgraded to the X7500 from a Universal and prior to that I was using a Magician.
The Ameo runs vids better than both those devices. I have my display driver set to ATI imageon with No hardware acceleration within TCMP and Coreplayer and I get GREAT results. It will happily play any 700 - 800 MB DIVX/XVID .avi file which I download to be used on a PC. I dont ever do any conversions unless I have to rip from a DVD.
I think that the Ameo is a great device to play videos on, much better than my N95 and my PSP.
Is it just popular to offer bounties? Best place to do that is to donate to Athena project for more ROM goodness
Requests/suggestions please for WM 6.1 cookers considering their next release:
- 64 MB Program Memory
- Absolute bare skeleton WM 6.1
- essential candidates for removal:
> customer feedback
> windows live
> any windows help & support related bloatware
> error reporting
> search
> windows media player
> any animated items, icons, etc..
> junk items under \windows; unnecessary gif,jpg,bmp,png
etc, text files
- single boot screen, no splash, animations etc..
minimize WM 6.1 boot time
- removal of other misc bloatware, vaporware that are not
core to the function, speed and stability of WM 6.1
======================================================
To the site Administrators:
-------------------------
- can we initiate a donation bucket in which people may contribute
and pool donations?
- 1 month period (or other) in which donations can be collected and
cookers may submit their best releases
- the people (users) vote during the period on what they find to be
the most efficient, stable, fast, clean and best performing rom.
- at the end of the period the donation pool is distributed to the top 3
most voted cookers, e.g. 60%/25%/15% respectively.
======================================================
Suggestions, ideas, recommendations, criticism etc certainly
welcome.
Thanks to all
--kara
64M program memory mean No WM.
why?
is there a maximum?
Thanks,
ks1781 said:
why?
is there a maximum?
Thanks,
Click to expand...
Click to collapse
you are really someone )
Trinity have only 64MB build in , how come it have 64MB program memory ? DId you have brain ?
--yes,
if the device has 64 MB SDRAM, why is it that most cooked roms
generally present approx. 50 MB of that?
is this a limitation or is missing 14 MB used for a special purpose?
Thanks for any advice.
?? because it takes up space to install the operating system.. even a 'bare bones' operating system is still an operating system..
did you ever wonder why there's space missing from your hard drive after you install windows xp?
http://www.htc.com/www/product.aspx?id=470
Memory ROM: 128 MB
RAM: 64 MB SDRAM
What is the ROM 128 MB designated for?
Thanks for your patience with me.
--kara
if i understand him correctly, he is referring to the program memory i.e. RAM not ROM. the 128MB ROM is meant for installation of OS (WM) where the 64MB RAM is the execution power. we normally get ~20MB-25MB RAM free out of 64MB total. i believed the rest (64MB - 25MB) was used for other services once WM started.
yes, that is what i'm trying to understand..
in this p3600 specification from HTC:
http://www.htc.com/www/product.aspx?id=470
it lists>
128 MB ROM
64 MB RAM
=================================================
for the 128 MB ROM
I assume the 128 MB ROM contains the OS installation, with
some component of this ROM hidden/reserved.
E.g. some cooked roms released have 'Big Storage'
~70 MB available to the user for NV storage
the remaining 58 MB comprises OS installation and a reserved
area.
=================================================
for the 64 MB RAM
This is the volatile memory available for the OS to boot & run, and
for program execution.
However, on most cooked roms I have used, under
Settings -> System -> Memory
'Program Total' is reported as ~50 MB.
So my question is - where is the remaining 14 MB RAM??
as dum as it sounds i've wondered about that too
even formatting issues aside (like how hard drive capacity is always lower than reported), 14MB seems like a lot to 'go missing'.
why doesnt WM even report it? because its being used by the system for services? so then why does it ALSO report itself using around 20MB of what's left?
that way, it's like 14 MB used (hidden) + approx. 20MB reported (shown) = approx. 34MB total? :/ hmm
ks1781 said:
So my question is - where is the remaining 14 MB RAM??
Click to expand...
Click to collapse
OK - You have a PC with 1GB of RAM say. Once say windows xp has booted up - your AV started etc. you probably have 684MB say of RAM left, so Where did the other 340MB of RAM go to?
Think about it.
wtf i still don't get it... dont be mad
i mean mine reports 2096236 KB... a full 2048MB of RAM
BUT of course 100-300 minimum will always be in use for the system itself
whereas in WM, it reports like 48MB total, AND say approx. 20MB in use
ok so the 20MB minimum in use will ALWAYS be in use because of windows mobile itself. FINE.
but why does it only represent 48MB as available?
and if that is the case, there's that missing unreported 12MB, PLUS that minimum 20MB always in use
that's what im curious about
Just think that Windows XP takes 250/300 mb of ram space....
PS: Please edit your title... Someone could understand that you really have a 64mb free ram rom......
joncgde2 said:
wtf i still don't get it... dont be mad
i mean mine reports 2096236 KB... a full 2048MB of RAM
BUT of course 100-300 minimum will always be in use for the system itself
whereas in WM, it reports like 48MB total, AND say approx. 20MB in use
ok so the 20MB minimum in use will ALWAYS be in use because of windows mobile itself. FINE.
but why does it only represent 48MB as available?
and if that is the case, there's that missing unreported 12MB, PLUS that minimum 20MB always in use
that's what im curious about
Click to expand...
Click to collapse
Maybe it is for the Radio Rom etc...or maybe Microsoft are stealing Ram and stockpiling it....lol
This is actually a valid question.
The system has 64MB of ram, some how 14MB of this ram is allocated away before the OS loads. This leaves 50MB of ram left for the OS, which uses about 20 MB and leaves 30 MB of ram for applications.
I think everyone understands this part.
The question is, what part of the phone is pre-allocating 14MB of ram.
My only guess is the videocard, if not that then it might be the pagefile.
tetsuo55 said:
This is actually a valid question.
The system has 64MB of ram, some how 14MB of this ram is allocated away before the OS loads. This leaves 50MB of ram left for the OS, which uses about 20 MB and leaves 30 MB of ram for applications.
I think everyone understands this part.
The question is, what part of the phone is pre-allocating 14MB of ram.
My only guess is the videocard, if not that then it might be the pagefile.
Click to expand...
Click to collapse
Does it really matter where it goes? Obviously if that memory hasn't been exploited yet by the excellent cookers etc in here....then it can't be of any benefit.
I concur with tetsuo55.
The reasoning proposed by Andych and others still does not quite
correlate.
i.e. 64 = 14 (OS) + ~20 (progs) + ~30 free
the ~20 is supposedly attributed to basic progs,
e.g. phone, filesys, mail etc..
A listing of such process summates to approx. 8 MB total.
That still leaves 12 MB of unaccounted for basic function
and userland process consumption.
Regarding the ATI video chip, general investigation and
settings check of tcpmp would suggest at best it is a
4 MB chip (whether dedicated or shared)
I cant see the 'remaining ~14 MB' that I'm searching for
being used for paging. Paging is part of overall virtual memory,
and involves page outs/ins to a location on some type
of physical media. Additionally, with the usual ~ 30 MB
ram free, in the context of these devices, a swap requirement
is unlikely given the 'free' memory available.
Although 14 MB may seem peanuts compared to standard desktop
ram configurations today - with a p3600 + WM, recovering the
14 MB (if possible) would provide a much welcomed bonus to
the trinity.
--kara
ahh now we're onto something good work ks1781...
i fully agree with the need to just find out the answer to this... most likely it's something that will be perfectly explainable and make sense and we won't be able to do anything once we find out
but it sure would be nice to know
OK I have the 'answer' - straight from a Windows Mobile blog - I'll post it here cos it's all straight to the point and interesting (somewhat) Link is HERE
The Page Pool
Applications use RAM in two ways. There is code that runs, and there is data that is created while it is running. On a NOR device, the code can run directly from the ROM and not be loaded into RAM first. This process is called XIP (eXecute In Place). NAND devices can't XIP, so their code is loaded into RAM and executed from there. If you don't have a Page Pool, this code is loaded into normal RAM. The Page Pool is a mechanism to limit how much code is loaded into normal RAM. With a Page Pool, we can unload code that hasn't been used in a while and reload it later if we need to. We can't do that without a Page Pool.
On a typical NAND-based WM5 device, the Page Pool is 4.5M.
The Radio Stack
Devices with a Cellular Radio have a complicated bunch of code to make their radios talk to cell towers. On some devices, the radio is a self-contained module with its own RAM and ROM. On others, the radio code is stored in the normal system flash. If so, it either needs to XIP, or it needs to be run in RAM. If it's run in RAM, that RAM is taken away from the system.
A typical radio stack takes 4M.
DMA Buffers
Some hardware can write directly into RAM without using the CPU to do it. This is called "Direct Memory Access" or DMA. DMA is very efficient and lets you get a lot more data transferred in the same amount of time, usually for less power. But it's best to set aside your DMA buffers before the system boots. This guarantees that they're there when you need them. PocketPCs have been doing this for a decade. But, back in the old days, the main use for DMA was audio capture. Audio data is small, so the DMA buffers are also small. Video, on the other hand, is big. More data requires bigger DMA buffers.
An OEM will tune the size of the pre-allocated DMA buffers based on what the device is intended to do. If the main goal is still photos, you can use a much smaller buffer. If the goal is recording video, it needs a much larger buffer. If the goal is video conferencing, it needs a bigger buffer still.
DMA buffers range in size between 300K and 6M. For a video capture device, it's likely to use around 4M.
XIPKernel
There are portions of the deepest parts of the OS that have to XIP. If you're on NOR, that code just XIPs like everything else. Not so on NAND. For a NAND system to boot, it needs to load this code into RAM first and then run it from there. When the system is running, it can't really tell if it's running from RAM or ROM, so it assumes it's running from ROM and doesn't count this space.
The XIPKernel region tends to be between 1.5 and 2M.
The Frame Buffer
There is a chunk of RAM set aside to hold everything that's on the screen. (If you want to know more about it, read this.) On most devices, every dot on the screen needs two bytes. A typical Pocket PC has 240x320 dots. That would be 300K. If you have a 640x480 screen, it's 600K. Sometimes, for performance reasons, devices will have two frame buffers. So this could take up to 1.2M.
Click to expand...
Click to collapse
Thanks joncgde2 - good find which provides a sufficient explanation as to the 'hidden' 14 MB.
There is still another question.
WM reports ~24 MB in use (per earlier screen captures) - where 'in use'
is attributed to running applications.
Checking a process listing via task manager shows the total
apparent RAM in use by these 'running applications' to be ~8 MB.
Can anyone provide an explanation to account for the
remaining ~16 MB??
Hi,
There has been a LOT of information said in previous forums on changing pagepool and its effect. But rather spread out, and rather confusing when investigated, and but not specifically for our HD
So in this thread can you post your experiences on what, how and why you changed your pagepool settings to.
Can you include...
1. What ROM you used when you changed the pagepool
2. How did you change it? Eg program etc...
3. Why did you go up/down?
4. How did it effect the a) speed, b) memory balance, c) program function in the ROM.
The program that I used is found here...
http://forum.xda-developers.com/showthread.php?t=323269
But is there a way to change the pagepool without having to flash the rom again (one that requires only a soft reset)?
I would like to make up a table of experiences so that people can make informaed decisions...so the more data we get on this the better!
EG. I am using the Energy 21908 July 10 Dinik CHT rom...I changed it from 22MB to 24 MB.
I feel that it is more responsive when jumping between screens, and slightly quicker. The memory has remained about the same, but I have not used it long enough to comment on program usage...will update later.
Please post past and present experiences...
Regards
J
I used the same tool you used. Ive tried changing the pagepool from 12mb to 16mb, 32mb and 4mb. I did not see a significant difference between the default 12mb and the 16mb and 32mb. 4mb is not good as it cannot even load calendar. so I decided to go back to the default 12mb pagepool. I think 12mb is already the optimum pagepool for the HD with stock 1.56 rom
I have been searching for quite a while (~2 weeks) & have not been able to find anything that helps me do what I want. I have been working on a modified HD2 ROM for my TMOUS HD2 {based on 2.13 ROM}. I have made many changes & have been able to apply most all the mods that interest me the most. There are many references to my problem; but no permanent fixes, & I am tired of the the tempory fix.
The tweak that has eluded me is the "FlashPowerUnavailable" registry entry. I have traced everything within the ROM & could not find the registry setup for this feature. After an extensive search thru all the .DLLs, I was finally able to find the settings. They are located in Battdrvr.dll. From what I understand; the .DLL reads the battery level & automatically inserts a registry key that disables the camera's flash whenever the battery level reaches 20% or less. Even if you delete the registry entry, the .DLL will reinsert it as soon as the battery goes below 20%. Personally I am tired of having to edit the registry everytime I want to take a pic when the battery level is low. The flash adds no real power drain & therefore the "FlashLightPowerUnavailable" is a BS setting that is completely unneeded.
So, here is my question to the community. Is there anyone that can rewrite the HD2's Battdrvr.dll so as to remove any reference to the "FlashLightPowerUnavailable" registry? If it's not possible to remove it completely; is there a way to change the trigger from 20% to 1%?
With the exception of changing graphics & text; I will not even pretend to know what I am doing when it comes to modifying a .DLL file. As such, I have not even attempted to modify this .dll. I have PEexplorer, Restorator, & ResHack on my machine, but I only use them for editing graphics & icons {& occasionally text}. If someone could modify the .dll, I would be extremely grateful. Of course; I'm sure that I am not the only one that would like to have this mod done. Of course; I am also willing to try & learn if someone would want to walk me thru modifying a .dll file.
I have attached BattDrvr.dll in the below .7z file. The zipped folder contains the original module {pulled from 2.13.531.1}, as well as the actual .dll itself. Any help is greatly appreciated.
Thanx:
Hippie
I'm not too familiar with Battery drivers but if you could find a way to have it be associated with Power Saving Mode you could just have power saver kick in at %1..?
But like I said I have no idea how it works..
Sorry for the delayed responce.
BattDrvr adds a registry entry when the battery reaches 20%. It is also readded to the registry upon every reboot. One would need to create an event to monitor the status of the reg entry, & delete/change it when it is activated. Personally; I am not real familiar with the event system & have not dealt with it too much {except to deactivate events thru DotFreds task mngr}.
Would creating an event utilize any system resources? I am trying to do this without adding another footprint to the system {no matter how small}. I know that modding the .Dll will accomplish what I want without creating any new footprints. This is why I posted this question to the community to begin with.
Personally I can't believe that this hasn't been done already. I also can't believe that there seems to be no interest in this whatsoever. I can't be the only one that uses the flash after the battery is below 20%.
I didn't test it, don't have device
What i did was:
Open hex editor, Search for "00 53 E3 35 00 00 9A 1C 37 91 E5 02 00 53 E3" the number before that found should be "14" (which is "20" in decimal) change to "01" (which is "1" in decimal).
I used IDA and HxD
The modded file is in attachment
Vico100 said:
I didn't test it, don't have device
What i did was:
Open hex editor, Search for "00 53 E3 35 00 00 9A 1C 37 91 E5 02 00 53 E3" the number before that found should be "14" (which is "20" in decimal) change to "01" (which is "1" in decimal).
I used IDA and HxD
The modded file is in attachment
Click to expand...
Click to collapse
Little Off topic .. but you seem to know howto hex edit stuff
Been woundering why no one has hexed skyfire so it doesnt check for the skyfire server .. and just goes to google or so other website ..
I was able to get SkyFire working today kinda .. by "tricking" it and made it goto google .. after that .. I was able to surf NP ..
Just a thought
hmmm..i don't know about android...never tried.
Vico100 said:
hmmm..i don't know about android...never tried.
Click to expand...
Click to collapse
No No .. Skyfire is also for WM
Vico100 said:
I didn't test it, don't have device
What i did was:
Open hex editor, Search for "00 53 E3 35 00 00 9A 1C 37 91 E5 02 00 53 E3" the number before that found should be "14" (which is "20" in decimal) change to "01" (which is "1" in decimal).
I used IDA and HxD
The modded file is in attachment
Click to expand...
Click to collapse
Glad I found this. Will try it out when TMOUS sends me my two free HD2s. Thanks. If anyone can report back as to weather it works or not, please do. Might take me a while since mine are on backorder.