Related
Hello,
After flashing Alcaline's WM6.1 standard ROM for the Wings, I began researching Internet Explorer Mobile.
I came across a very interesting feature called FastBack, however, I don't understand how to write the DWORD value. The value is derived from a LOWORD and a HIWORD. I did some research on those, but can't make much sense out of it and was hoping some of you devs could help out.
Does anyone have any experience working with LOWORD and HIWORD? Can anyone make sense of combining the two to create a DWORD?
Thanks!
Matt
HIWORD * 65536 + LOWORD = what you need.
Koterpillar said:
HIWORD * 65536 + LOWORD = what you need.
Click to expand...
Click to collapse
Thanks for the reply.
So, if I understand correct, to calculate the DWORD that would be the FastBack DWORD value, for 8 pages and 2048KB cache the value would be:
2048 * 65536 + 8 = 134217736
That seems really high. But, that could be correct. FastBack is currently functional with a DWORD value of 8092.
Please confirm.
Also, what could be done about a Forward caching? As in, would it be possible to create some kind of IE mobile add-on that allows you to enter an "Offline caching mode" that will begin to cache forward and back? I'm seriously interested in this as a solution to reading NY Times on the subway.
Thanks,
Matt
Hi there,
as anounced her is my first Umbrella Themed Android Rom. It is a mixture of several vogue, dream and saphire roms.
Here the things i added:
Some apps:
-proPaint Camera (fully working)
-RockOn
-LastFM app
-Custom boot animation and sound (just on first boot so loud)
-Umbrella Themed (more to come, if some graphical advanced people could help me i would be pleased)
-Latest Libs
-Shazaam
-New default ringtone and notification tone
-Kaiser wifi fix
Working:
Kaiser (tested by me:
-Data
-WiFi
-Camera (proPaint)
-Audio
-Phone (very responsive)
Vogue: Please tell me and i will add infos!!!
-Data ??
-WiFi ??
-Camera (proPaint) ??
-Audio ??
-Phone (very responsive) ??
I'm no developer i only wanted to give something back to this great community. Thanks goes to: dzo, Zenulator, mssmission, enatefox, pmos, vilord, craig0r, and all the others i forget taht make android on our devices possible
Download Link: Umbrella Corporation v2, with working media ROM
OPTIONAL:
Here my startup.txt (Change for your carrier to get data!!!)
#alloctest 0x2000
set RAMSIZE 0x07000000
set RAMADDR 0x10000000
#set FBDURINGBOOT 0
set MTYPE 1553
set KERNEL zImage
#set initrd "initrd.gz"
set initrd "\Storage Card\initrd.gz"
#set initrd "\Storage Card\initrd-console.gz"
#set initrd "\Storage Card\android.bin"
#
# The following kernel parameters are useful
# ppp.username - The username used to connect to the network when dialing #777
# ppp.password - The password used to connect to the network when dialing #777
# msm_sdcc.msmsdcc_fmax - The maximum frequency (in Hz) used by the SD controller
# pm.sleep_mode - The mode used when the phone is off
# 0=Power Collapse Suspend, 1=Power Collapse, 2=Apps Sleep,
# 3=Slow Clock and Wait for Interrupt 4=Wait for Interrupt
# Default is 1, use 1 for best power savings
# board-htckaiser.panel_type - Panel type used to power the panel off and on
# 0=Don't power off the panel (Default)
# 1=Sony 2=Topoly 3=Topoly (probably just the same as 2)
#
set cmdline "clock-7x00.ahb_div=3 clock_7x00.slow=1 elevator=noop ppp.nostart=0 board-htckaiser.panel_type=1 ppp.apn=internet.t-mobile ppp.username=tm ppp.password=tm pm.sleep_mode=1 mddi.width=320 mddi.height=480 msm_sdcc.msmsdcc_fmax=32000000 no_console_suspend board-kaiser-keypad.atttilt=0"
boot
Click to expand...
Click to collapse
and my custom.hero.conf: !!just works if your card is partitioned!!
Klick
Have fun!!!!
Aside from looking rad, does this ROM do anything for us? is it faster due to the removed apk's? I love the Rogers builds, but they freeze/crash on me too often for my liking.
I removed some of the apps, like all thoose who use the g-sensor, also some unneded media files for now, as i've said this is just the first test. If all works well for you ( i got gps, data, wifi, and media files working on my kaiser) i start to tweak it, but the hero from kingklick is very fast and the rom is more responsive than many heros around here. And for me no force colse until now. ( i'll update the thread later, when back home i will tweak some other features)
Is this a real Android rom? or just a bare bones Windows ROM to run Android on top?
I need a lot more details before I can even consider using this.
slow88lx said:
Is this a real Android rom? or just a bare bones Windows ROM to run Android on top?
I need a lot more details before I can even consider using this.
Click to expand...
Click to collapse
This is as much and Android ROM as every other android ROM on the Vogue forum. It is a system image to run Android with via Haret, instructions as to such you can find in other threads/links around here.
craig0r said:
This is as much and Android ROM as every other android ROM on the Vogue forum. It is a system image to run Android with via Haret, instructions as to such you can find in other threads/links around here.
Click to expand...
Click to collapse
Ahh I see. I haven't used Android since Dzo first started with it. I was half hoping someone had finally build some semblance of a ROM with Android.
It sure looks awesome and it would be cool to have the actual Sense UI as opposed to the half ass versions I'm using on SPB MS3 and PointUI
New Version added on first post
doesnt work for me i used all ur basefiles and ur system file, deleted the existing data file.
also replaced my startup.txt with yours and it gets stuck in Loading System
using a kaiser w windows mobile 6.1
Reboot and give it some time
its good to see new stuff. keep it up.
its good to see new stuff. keep it up.
Click to expand...
Click to collapse
Thanks, will see what i can. I have mouch to learn... When i fixed one thing another thing occurs, but hey... that's the fun..
any screenshots of this build?
dude bomb azz boot screen. haha it was so loud it gave me a heart attack then i turned into a zombie.
You got no Anti-Gen at home?
How do you adjust the startup.txt for the vogue? When I run haret it tries to locate the SD card constantly.
On the androidonhtc site you found several infos on how to edit startup /default.txt
Hey everyone
I was wondering if there is a site like ( http://www.androidonhtc.com/ ) I knw it says vogue but theres no build there. I dont get if there is a data base for all the builds u guys make but i been looking here and am really not sure what build to try or where to get all files from.
If i am being a damn noob just point it out and give me a link to all the files i need for the best ion build or this beast ( http://www.youtube.com/watch?v=wbIytfDUBqM ) and yes i did search but all i see is u might need this rom or this image and i am just lost. like ( http://forum.xda-developers.com/showthread.php?t=544906) i read it it says all these new sweet builds but i dont see links. Where do i get all the base files from and the specific things to get these builds working sorry if i am being a noob but i wanna try android
read and find
http://code.google.com/p/vogue-android/downloads/list
woww lollll seems so simple now so i just scoop up a darn system image and i am good to go correct .. is haret already in the base files?
and http://code.google.com/p/vogue-hero/
yea what mssmison said
google is your friend, make it your bit**
Hey i got a question then i see there are 3 diff default.txt which one do i use? I am trying the jesture blur system
lgevo said:
Hey i got a question then i see there are 3 diff default.txt which one do i use? I am trying the jesture blur system
Click to expand...
Click to collapse
hey man check this out http://vogue-hero.googlecode.com/files/%21%21%21HOW%20TO%20for%20ANDROID%21%21%21
thanks jamezelle do i have to put anything in front of mddi.width=320 mddi.height=480 lcd.density=160 or do i just paste it in the end of the default.txt. if i seen how ppl arranged there's this would be simple I keep getting unknown keyword middi or other unknown words when i add lines unknown board basically everything i read that i attempt to put in i put in wrong because it says to do this and i learn visually its hard for me to read this and get where to put the stuff
I got mine looking like
(
set RAMSIZE 0x08000000
set MTYPE 1667
mddi.width=320
mddi.height=480
lcd.density=160
board-htcvogue.panel_type=2
set KERNEL zImage
set initrd initrd.gz
#
#
)
whats with the ppp.username do i have to put that in? is there premade sprint default.txt? cause that what it said in the how to for android.
lgevo said:
Hey i got a question then i see there are 3 diff default.txt which one do i use? I am trying the jesture blur system
Click to expand...
Click to collapse
I suggest trying to run an Ion build as your first build. That way you can see the real speed and usability we have. The hero builds are cool, but IMO too slow for actual use although some people disagree.
lgevo said:
thanks jamezelle do i have to put anything in front of mddi.width=320 mddi.height=480 lcd.density=160 or do i just paste it in the end of the default.txt. if i seen how ppl arranged there's this would be simple I keep getting unknown keyword middi or other unknown words when i add lines unknown board basically everything i read that i attempt to put in i put in wrong because it says to do this and i learn visually its hard for me to read this and get where to put the stuff
I got mine looking like
(
set RAMSIZE 0x08000000
set MTYPE 1667
mddi.width=320
mddi.height=480
lcd.density=160
board-htcvogue.panel_type=2
set KERNEL zImage
set initrd initrd.gz
#
#
)
whats with the ppp.username do i have to put that in? is there premade sprint
default.txt? cause that what it said in the how to for android.
Click to expand...
Click to collapse
you shouldnt have to mess with ppp.username and ppp.password and board-htcvogue.panel_type=2 should be fine since you say you see the htc screen right?
you should be good to go
the screen went with so i tried 2 but now it still gose white so i am gona try 3
i still get unknown keywords mddi, mddi, lcd, board, and the. I must have something wrong this happens when i hit run in haret
lgevo said:
i still get unknown keywords mddi, mddi, lcd, board, and the. I must have something wrong this happens when i hit run in haret
Click to expand...
Click to collapse
You're doing it wrong, you should be editing what is already there, not adding new stuff.
Find the appropriate stuff in the file that is already there, and change it to what you need. You completely messed up your default.txt, so I would start with an untouched copy, and then edit it, changing only what is needed.
ok so i should add it to the mess of stuff at the bottom? this
(
The following kernel parameters are useful
# ppp.username - The username used to connect to the network when dialing #777
# ppp.password - The password used to connect to the network when dialing #777
# msm_sdcc.msmsdcc_fmax - The maximum frequency (in Hz) used by the SD controller
# pm.sleep_mode - The mode used when the phone is off
# 0=Power Collapse Suspend, 1=Power Collapse, 2=Apps Sleep,
# 3=Slow Clock and Wait for Interrupt 4=Wait for Interrupt
# Default is 3, use 0 for best power savings
# board-htcvogue.panel_type - Panel type used to power the panel off and on
# 1=Hitachi 2=Topoly 3=Samsung
# clock-7x00.mddi - MDDI clock (try 0xa51 or 0xe2c)
# clock-7x00.ahb_div - Advanced Host Bus divider, default is 4
# 2 is faster but uses more power
# clock-7x00.a11 - ARM11 clock speed in MHz, best to leave this alone
# ril.smsfix - Bell SMS works better with this set to 1
# lcd.density - Defaults to 160, 128 shows more on screen, you'll want to adjust the mddi width and height too
# vogue-ts.XMIN - xmin value for the touchscreen calibration. Also YMIN, XMAX, YMAX, PMIN, PMAX.
#
# Probably the only one of these you will need to change is the panel type, NZ Vogues seem to all have type 1
# US Sprint vogues usually have type 2 or 3 I think.
# Make sure you add these between the quotes on the following line and that your editor hasn't split the line up.
set cmdline "[email protected] ppp.password=telecom mddi.width=320 mddi.height=428 msm_sdcc.msmsdcc_fmax=32000000 pm.sleep_mode=0 board-htcvogue.panel_type=3 no_console_suspend"
boot
)
lgevo said:
ok so i should add it to the mess of stuff at the bottom? this
(
The following kernel parameters are useful
# ppp.username - The username used to connect to the network when dialing #777
# ppp.password - The password used to connect to the network when dialing #777
# msm_sdcc.msmsdcc_fmax - The maximum frequency (in Hz) used by the SD controller
# pm.sleep_mode - The mode used when the phone is off
# 0=Power Collapse Suspend, 1=Power Collapse, 2=Apps Sleep,
# 3=Slow Clock and Wait for Interrupt 4=Wait for Interrupt
# Default is 3, use 0 for best power savings
# board-htcvogue.panel_type - Panel type used to power the panel off and on
# 1=Hitachi 2=Topoly 3=Samsung
# clock-7x00.mddi - MDDI clock (try 0xa51 or 0xe2c)
# clock-7x00.ahb_div - Advanced Host Bus divider, default is 4
# 2 is faster but uses more power
# clock-7x00.a11 - ARM11 clock speed in MHz, best to leave this alone
# ril.smsfix - Bell SMS works better with this set to 1
# lcd.density - Defaults to 160, 128 shows more on screen, you'll want to adjust the mddi width and height too
# vogue-ts.XMIN - xmin value for the touchscreen calibration. Also YMIN, XMAX, YMAX, PMIN, PMAX.
#
# Probably the only one of these you will need to change is the panel type, NZ Vogues seem to all have type 1
# US Sprint vogues usually have type 2 or 3 I think.
# Make sure you add these between the quotes on the following line and that your editor hasn't split the line up.
set cmdline "[email protected] ppp.password=telecom mddi.width=320 mddi.height=428 msm_sdcc.msmsdcc_fmax=32000000 pm.sleep_mode=0 board-htcvogue.panel_type=3 no_console_suspend"
boot
)
Click to expand...
Click to collapse
Code:
set cmdline "[email protected] ppp.password=telecom mddi.width=320 mddi.height=480 lcd.density=160 msm_sdcc.msmsdcc_fmax=32000000 pm.sleep_mode=0 board-htcvogue.panel_type=3 no_console_suspend"
boot
thanks for all the help i just realized why it seemed so difficult because my text editor was not putting each thing on there own line so it looked like a HUGE jumbled mess and then when i pasted it in the quick reply i realized that it wasnt seperated right in the txt but in these replies it worked perfect anyway thanks alot everyone! if anyone can gimmie tips on what settings they used for a sprint vogue because now at least it get to the linux part but i can get into it yet but i will keep trying i am so pumped to try android!
Hey ok i am gettin the "could not find superblock blah blah blah... i was reading about partitioning the sdcard to fix this is this really a must?
OMFG
ahah sry everyone for being a damn noob I forgot to name the systemsdfsdfd.img to just system.img ahaha omg thanks alot to all the devs and just everyone that helped me sry for being a noob
hello everybody here in xda
I was wondering What is The Best File system cache size for different Pocket Pc's
and My question is
What is the Best File system cache size For all pocket pc's with wm6.5 Or wm6.1 ?
edit : the answer is in the next post I think
cheers
3 things:
1. Jeez, change the alignment on your post, it's annoying (edit: done, thanks, lol).
2. You have to set the caches in boot.rgu; it doesn't work changing them anywhere else. The caches are set in early boot, and making changes to the system registry does nothing.
3. The value 'cachesize' is obsolete; changing it does nothing. MSDN says this in its file system cache page.
Code:
[HKEY_LOCAL_MACHINE\System\StorageManager\FATFS]
"FriendlyName"="FAT FileSystem"
"EnableCache"=dword:1
"CacheSize"=dword:0
The value you want to mess around with is mainly the datacachesize, and maybe the fatcachesize. In my experience, it doesn't make a hell of a lot of difference. You have more ram at boot with a lower datacache, though. If you make the datacache too large, the device won't boot. The stock setting is pretty big (8 MB). These are stock values in the raphael native kernel:
Code:
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FLASHDRV\FATFS]
"DataCacheSize"=dword:00000800 ;2048 sectors(2048*2048=4MB)
"FatCacheSize"=dword:00000100 ;256 sectors(256*2048=512KB)
Farmer Ted said:
3 things:
1. Jeez, change the alignment on your post, it's annoying.
2. You have to set the caches in boot.rgu; it doesn't work changing them anywhere else. The caches are set in early boot, and making changes to the system registry does nothing.
3. The value 'cachesize' is obsolete; changing it does nothing. MSDN says this in its file system cache page.
Code:
[HKEY_LOCAL_MACHINE\System\StorageManager\FATFS]
"FriendlyName"="FAT FileSystem"
"EnableCache"=dword:1
"CacheSize"=dword:0
The value you want to mess around with is mainly the datacachesize, and maybe the fatcachesize. In my experience, it doesn't make a hell of a lot of difference. You have more ram at boot with a lower datacache, though. If you make the datacache too large, the device won't boot. The stock setting is pretty big (8 MB). These are stock values in the raphael native kernel:
Code:
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FLASHDRV\FATFS]
"DataCacheSize"=dword:00000800 ;2048 sectors(2048*2048=4MB)
"FatCacheSize"=dword:00000100 ;256 sectors(256*2048=512KB)
Click to expand...
Click to collapse
I have not the FLASHDRV key in HTC HD2.
NIKOSXRI said:
I have not the FLASHDRV key in HTC HD2.
Click to expand...
Click to collapse
Well, just look for datacachesize in the boot.rgu; the storage profile just has another name, I guess.
thanks for reply Farmer Ted
Farmer Ted said:
Well, just look for datacachesize in the boot.rgu; the storage profile just has another name, I guess.
Click to expand...
Click to collapse
Thanks, you got it, I have datacachesize dword hex400 and fatcachesize dword hex200 in my HTC HD2.
Which do you think is the best values for this phone?
..you know guys....
[HKEY_LOCAL_MACHINE\System\StorageManager\FATFS]
"CacheSize"=dword:00000800
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC2\FATFS]
"CacheSize"=dword:00000100
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC2\FATFS]
"DataCacheSize"=dword:00000100
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC1\FATFS]
"CacheSize"=dword:00000100
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC1\FATFS]
"DataCacheSize"=dword:00000100
[HKEY_LOCAL_MACHINE\System\StorageManager\Filters\fsreplxfilt]
"ReplStoreCacheSize"=dword:00000100
[HKEY_LOCAL_MACHINE\System\StorageManager\FATFS\Filters\fsreplxfilt]
"ReplStoreCacheSize"=dword:00000100
[HKEY_LOCAL_MACHINE\Snd\Event]
"EventCache"=dword:00000100
and PP, of course.
filesys.exe vs file system cache
Hi Farmer Ted,
Thanks for the explanation.
Farmer Ted said:
2. You have to set the caches in boot.rgu;
3. The value 'cachesize' is obsolete; changing it does nothing. The value you want to mess around with is mainly the datacachesize, and maybe the fatcachesize. You have more ram at boot with a lower datacache, though. If you make the datacache too large, the device won't boot.
Click to expand...
Click to collapse
I'm facing a problem in my device with the filesys.exe.
There are certain processes (Manila contacts and PimBackup) which make the filesys.exe to use up to 95% of CPU making the device unusable. (details on the link on my signature).
I'm wondering if there is any relation between the filesystem cache and the behaviour of filesys.exe.
What will happen if the cache is set to 0?
Thanks in advance
I kind of doubt the cachesize is affecting the cpu load. I'm not sure what would cause that issue, especially with pimbackup. Adjusting the caches size affects how much RAM filesys.exe uses. If you profile the virtual memory of the device with virtualmemory.exe or with devhealth.exe, you'll see a larger or smaller virtual memory commitment for filesys.exe in slot 2 depending on the size of the caches.
If you set the caches to 0, then the system decides what cachesize to use at first boot. In my experience, it's usually around 2-3 MB total (including fat, data, and I guess the bitmapcache). It works pretty well, I've set it as 0 and used it quite a bit that way. If you want no caching, then you need to set 'enablecache' to 0.
Cache size vs battery life
Hi guys,
In your experience, does the different cache sizes/pagepool affects the battery life?
I don't think that either has much effect (if any) at all.
I need help, no chips HYB... (total 512Mbit = two real 256Mbit) were found me, but other (512Mbit) in my local. And there was these are soldered after the system has been successfully started and honestly showing 64Mb, but after upgrading to WM6 128MB is still available only 64Mb instead of the expected 128Mb.
The fact that the processor PX270 addresses a memory only 512Mbit for SDRAM partition by default. So no problem the trick with increasing RAM works with HYB... chips (two 256Mbit)
However, the CPU can address memory 2048Mb (what I need for my solution 512Mbit).
I think that the values of the registers are set likely bootloader or kernel os.
By this I needed help, how to find where these values are specified in the bootloader or image and how to change it?
Question to a respected ROM-maker:
What method have added support for 128Mb support???
I want to understand why not working set 512Mbit chips.
strange that no body knows or is it a "big secret".
I am upset, but if these chips will work, then it is possible to install other 512Mb and get a 256Mbyte in the end...
Have you tried Android and see what that detects?
Are you using a ROM that supports 128MB? I think for most if not all WM6.1 and above the cooks made this change. Also, I believe there was also a solder link/break to be made as well as soldering the new chips - have you done this too?
gquipster said:
Have you tried Android and see what that detects?
Click to expand...
Click to collapse
Nice idea, I have been thinking about it. I will try this weekend.
-Jonny- said:
Are you using a ROM that supports 128MB? I think for most if not all WM6.1 and above the cooks made this change. Also, I believe there was also a solder link/break to be made as well as soldering the new chips - have you done this too?
Click to expand...
Click to collapse
Yeah, I tried several ROM with supports 128MB.
Soldering done well, then I think there is no reason to worry.
I read the forum again on similar topics. And I think here it all the same to configure the processor, it registers may. Usually set by bootloader.
Such as SDRAM MDCNFG Register (MDCNFG).
Bits 31, named MDENX.
0 = Use normal 256-Mbyte memory map. By Default. 4 chips x 512Mb x 32bit or 8 chips x 512Mb x 16bit (64Mbyte) max.
1 = Use large 1-Gbyte memory map.
Bits 6:5 (DRAC0):
SDRAM Row Address Bit Count for Partition Pair 0/1
0b00 = 11 row address bits
0b01 = 12 row address bits
0b10 = 13 row address bits* BY DEFAULT
0b11 = reserved.
Bits 4:3 (DCAC0):
SDRAM Column Address Bits for Partition Pair 0/1
Use in conjunction with DCACX0 (DCACX0 concatenated with DCAC0)
0b000 = 8 column address bits
0b001 = 9 column address bits* BY DEFAULT
0b010 = 10 column address bits
0b011 = 11 column address bits
0b100 = 12 column address bits
As a result, in my understanding:
My two 512 Mbit (2 x 64Mbyte) installed in one SDRAM Partition 0 (if MDCNFG[31]=0 then regardless of other settings will be available 64Mbyte only)
In the case of HYB... chips we have 64Mbyte installed in SDRAM Partition 0 and SDRAM Partition 1, so there is no need to change this register.
And more. 512Mb addresses as 13 Row Bits x 10 Column Bits.
As can be seen by default the system addresses 13 Row Bits x 9 Column Bits, which is sufficient for 256Mb (two stacked 256Mb = 512Mb HYB... chips)
Hence, one more question how do you know the current value of this register to know where to dig it. And, accordingly, if necessary, change them.
Or I still wrong in something?