Database Develop

Just got my O2IIi. And I have couple questiont about it.

I just got this unit on ebay from a UK seller.
According to the box and description, it somes with 128Rom and 128 SDRam
But under "Device Information" it shows I have a Ram size of 128MB
a Flash size of 64MB only
Is it normal, or did I get a chopped down version of the pda from ebay seller???
Also, It there a program the replaces the Phone Dial program or a better phone dialing program for IIi, that can provide better controls???
Since the dialing program along with the contacts currently in our phone is not very user friendly for Driving!...any suggetions appreciate.
I'm hoping to see a program like regular cell phone where u can just scroll down and see your phonebook and dial using just one hand..
Thanks

Look in the system information and see what model it is.

Walay,
my O2 XDA IIi says the same. I think it's correct, with the remaining 64Mb (see further down the device information) being used for storage (mine says 59.68Mb)
Doesn't look like you're being ripped off

Mine does too looking at it!
Start menu/Settings/System/Device Information
CPU: Intel(R) PXA272
Speed: 520 MHz
RAM size: 128 MB
Flash size: 64 MB
Flash chip type: 28F256L18
Data bus: 32 bits
Storage size 59.68 MB (That is the rest of the Flash Memory)
LCD: 240 x 320 TFT
Colors: 65536

SD RAM will more than likely be an SD card he included.
As for the devices memory, you have 128mb RAM which is devided between storage and running programs, and the ROM which contains the OS itself, and the Ext ROM which contains the installers for things like O2 Active UI, Skype, the fax software, and so on, and leaves you 64mb spare to use.
The 64mb left in flash ROM, or on SD card, will not be lost if you run the battery out completely, or hard reset the device, anything in RAM will be lost.

Memory in WM6

When i upgraded my Himalaya to WM5, I think I used used the 64 MB RAM version. I used the himaDOC tool to partition my device and give 64 MB to the RAM and 64 to storage.
Will that partitioning persist after I have upgraded to WM6? Ever since I installed WM6 my device is very very slow and it is because there's less than 3 MB of RAM left available. Here's what my machine says about its memory:
The ABOUT menu shows "Memory: 61.28MB"
The Hardware tab in Device Information shows RAM 128 MB, Flash 32MB, Storage Size 30.53MB
And when I go to Start > System > Settings > Memory, it shows Storage Total: 30.53 and Program Total 61.25MB
I am a little confused about what all these different types of memories mean. If anyone can clarify, i would really appreciate it. Also is there a way to increase the storage memory because with the total 30.53, 27 MB is always in use and with the remaining 4 MB, the device is painfully slow.

humayunl said:
And when I go to Start > System > Settings > Memory, it shows Storage Total: 30.53 and Program Total 61.25MB
I am a little confused about what all these different types of memories mean. If anyone can clarify, i would really appreciate it. Also is there a way to increase the storage memory because with the total 30.53, 27 MB is always in use and with the remaining 4 MB, the device is painfully slow.
Click to expand...
Click to collapse
If you have used DOC partitioning tool, you have 30.53 MB of storage ROM. The rest of ROM is your system and radio stack.
Your RAM is divided into 3 parts: program memory (actual RAM), RAM disk and page pool. They sum up to 128 MB. So, for example, if you have 32 MB of a RAM disk and a 32 MB page pool, you have 64 MB of a program memory left.

So from the numbers I see on my device, does everything seem good or is there anything I can do to further improve memory performance/allocation so that the things will be faster?

Do you have a RAMdisk enabled?
You know, there's no simple answer to "what configuration is better". If it were, you wouldn't have a choice It depends on how many programs you have installed, what exactly programs you're running, and so on...

Browser cache directly to storage card?

I've used Kaiser tweak to route downloads directly to the 4gig card that I have--I have about 70 megs of storage memory still left in the unit, so my file downloads are limited to just this. Is there a certain step I'm missing to be able to store temp. browser cache directly to card w/o directly affecting storage capacity? I've also used J.S. advanced Configuration Tool 3.2 (similar to Tweak) put in the appropriate settings, same result.

telegraph0000 said:
I've used Kaiser tweak to route downloads directly to the 4gig card that I have--I have about 70 megs of storage memory still left in the unit, so my file downloads are limited to just this. Is there a certain step I'm missing to be able to store temp. browser cache directly to card w/o directly affecting storage capacity? I've also used J.S. advanced Configuration Tool 3.2 (similar to Tweak) put in the appropriate settings, same result.
Click to expand...
Click to collapse
get hold of a registry editor and change the value of the "Cache, "Cookies", and "History" keys to the ones mentioned below.
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders]
"Cache"="\Storage Card\IE Mobile\Temporary Internet Files"
"Cookies"="\Storage Card\IE Mobile\Cookies"
"History"= "\Storage Card\IE Mobile\History"
cheers

Be aware however, some people have reported PIE crashing with cache on the Storage Card.

Any possibility to correct the forced 32K cluster size on 32GB SD cards?

Learned last night from Patriot Memory what I already knew without realizing it...with 32GB (only) SD cards on what appears to be any version of Android, the cluster size -must- be 32KB (I had tried both 64KB for performance and 4KB to reduce slack wastage) or you *will* encounter corruption (possible root cause for some of our SD-card-booting brethren?).
Google has no fix according to Patriot and this is a widespread problem (across phones and tablets), though I can't for the life of me figure out why.
Is this a kernel-level issue with the filesystem? Any idea of whether this is something that might get fixed for CM7 to make it even more compelling than it already is?
Rodney

Rodney, I think the answer is no, unless we were to go to NTFS which is not robustly supported. here is a reference for FAT32 cluster sizing and formatting. Informative but some what dated.
http://www.infocellar.com/hardware/harddrive-cluster-sizes.htm
anyway, for 32gb disk , 32k clusters are mandated.
FAT32 offers efficient 4KB clusters for partitions up to 8GB. The cluster size increases with the size of the partition, up to 32 KB for partitions over 32GB

DigitalMD said:
anyway, for 32gb disk , 32k clusters are mandated.
Click to expand...
Click to collapse
Microsoft seems to think differently, as they offer a number of different cluster sizes for that partition using FAT32, all of which work (on their OS). If you're saying it's the Linux FAT32 VFS that's busted, that's fine...but it's still busted.
Rodney

It's not busted, its just the way Fat32 works for compatability. That's why Linux has ext3 and Windows has NTFS. Fat32 is old, but universal.

It is busted, and there is no such "compatibility" rule. The web page you referenced is mistaken.
The _only_ valid rule, in Microsoft's own code, is as follows (assuming 512-byte sectors):
FAT32: 65,526 < Number of clusters < 268,435,446
So for a 32GB device, let's look at the number of clusters we create with various cluster sizes...
64KB: 500,000
32KB: 1,000,000
16KB: 2,000,000
8KB: 4,000,000
4KB: 8,000,000
2KB: 16,000,000
1KB: 32,000,000
512: 64,000,000
(no cluster size smaller than this because a cluster can't be smaller than a logical sector)
All of the above cluster sizes *are* supported by Microsoft, and *should* be supported by any "compatible" implementation of FAT32...thus, there is an _in_compatiblity with Linux's VFS implementation of FAT32 that does not adhere to the standard, and thus causes data corruption.
Don't believe me? Format a 32GB SDcard with 16KB clusters on a Windows box. Copy 100 100MB files to it, mounted directly to Windows, and check each for corruption. Repeat the test after inserting the SDcard into an Android device and USB-mounting it to the same PC. You _will_ see corruption, that _is_ specific to the Android device. I imagine it would be seen under other Linux distributions as well, but I've seen no anecdotal evidence and can't be bothered to test since the evidence is pretty clear.
Obviously, if 32KB were the only permitted/possible cluster size, Patriot wouldn't have had to warn all its customers about the risk of data corruption when _not_ using that cluster size.
All I wanted to know is whether anyone had even looked at it, cared to do so, or were even aware (within the dev community), so that a bit of attention might *possibly* be paid to it to save the long-term pain of users having (silently) corrupted data. It's the worst kind of data loss, and if it's an easy fix, worth doing...don't you think?
Rodney
P.S.: I'm not going to get into any further semantics wars. I am continuing to tire of the ego-positing on the forum. There's nothing wrong with being wrong (I know - I do it a lot!), but continuing to defend your position beyond that is both hopeless and counterproductive.
P.P.S.: It's worth noting this defect does _not_ exist for 16GB and smaller FAT32 partitions in Android. For those playing along at home, many of the files Android creates itself - and many I store on SDcards - are smaller than 32KB, so the whole point of the exercise in adjusting the cluster size downward is to avoid wasting space.

whatever man... just chill

DigitalMD said:
whatever man... just chill
Click to expand...
Click to collapse
Misinformation bugs me (no pun intended), because it leads to defects just like this. There are a great many resources on the Internet that are Just Plain Wrong(TM), Wikipedia notwithstanding (which I personally think gets a bad rap, but that's a whole different subject). If it weren't for the fact that this bug trashes user data without notice, I wouldn't care so much, but I pity the fools that come after me that format their SDcards with smaller cluster sizes thinking they are being clever about space usage only to find a large number of their files are toast. It's not fun.
Rodney

What are you going to do with the sd card?!
If you put 10000 files on it you will only gain 7,8 MB with a 16kb cluster size.

TDO said:
What are you going to do with the sd card?!
If you put 10000 files on it you will only gain 7,8 MB with a 16kb cluster size.
Click to expand...
Click to collapse
Actually, 10,000 1KB files with a 32KB cluster will result in 310MB of wastage - moving to a 16KB cluster size reduces the slack to 150MB. In practice, I have a -lot- more than 10,000 1KB files, largely emulator files...in fact, it's a bit worse, because each of those 1KB ROMs is zipped down considerably, so the real wastage is ~315MB for those files alone. Yes, this does represent only 1% of the total storage, but that's also a single directory.
Besides, I'm anal.
Rodney

http://support.microsoft.com/kb/314463
Maximum cluster size for FAT32 is 32K, but otherwise, sounds like something is busted.
Hard to believe since the FAT32 code should be coming from Linux mainstream which is pretty old at this point.

8GB space?!?!

So I brought the XL, and I knew that some space would be taken up from my "16GB", but is it really supposed to be only 8GB?

WillyVWade said:
So I brought the XL, and I knew that some space would be taken up from my "16GB", but is it really supposed to be only 8GB?
Click to expand...
Click to collapse
No. The 16GB is divided into phone storage (the equivalent of an SD card that cannot be removed) and internal storage.
The rest of the space is occupied by system stuff. So you get about 8-9GB of "phone storage" and about 3-4GB "internal storage".
Sent from my HTC Sensation XL with Beats Audio X315e using Tapatalk

Htc sensation xl storage allocation
Ahlan,
I wanted to share this with xda-developers forum, as I have seen the same question repeated on various forums.
This is about how 8.8 Gigabytes shows, when the HTC sensation XL is supposed to have 16 Gigabytes on.
HTC SensationXL has the specs of:
“Total Storage”: 16 Gigabytes (Actual calculated value is 14.90 Gigabytes)
“Available Storage”: Upto 12.64 Gigabytes (And this is the Actual calculated value)
“Total Storage” = “Available Storage” + “ROM Storage”
“Available Storage” = “Phone Storage” + “Internal Storage”
“Total Actual Storage” = “Phone Actual Storage” + “Internal Actual Storage” + “ROM Actual Storage”
14.90 Gigabytes = 8.89 Gigabytes + 3.75 Gigabytes + 2.26 Gigabytes
Where:
“Total Actual Storage” = Is the total calculated storage of the phone.
“Phone Actual Storage” = Is the calculated storage assigned for media files.
“Internal Actual Storage” = Is the calculated storage assigned for apps and apps data.
“Rom storage” = Is the calculated storage consumed by Operating system files (Android Gingerbread 2.3.5), user interface files (HTC Sense 3.5) and pre-installed apps (facebook, twittes, dictionary, HTC watch and all other apps you find installed on your phone when you first buy it)
Description of above mentioned terms is on the following
HTC SensationXL, is somehow special in the way it allocates the storage it has.
HTC SensationXL has no slot for external MicroSD card.
HTC has come up with a new phrase called “Phones Storage” to differentiate it from “Internal Storage”.
“Internal Storage”
- is a part of SensationXL total storage.
- is inaccessible if you plug your phone to your computer via USB.
- is assigned to contain apps you install or side load and to contain apps data.
Contacts are managed and stored by an HTC App Called “People”; data is stored to “Internal Storage”
SMSs are managed and stored by an HTC App Called “Messages”; data is stored to “Internal Storage”
E-Mails are managed and stored by an HTC App Called “Mail”; data is stored to “Internal Storage”
“Phone Storage”
- is a part of SensationXL total storage.
- is the storage you can access via USB-cable when connected to your PC.
- is assigned to include Media files you import from computer via USB-Cable or download to your phone from the internet.
Music files, Video files, Picture files and Office Files are stored to “Phone Storage”
Now, other terms should be highlighted.
"Nominal Storage” and “Actual Storage”
"Nominal Storage”
It’s the storage capacity you find written on any flash memory (actually any solid state storage, flash memory or large capacity storage).
That’s 2GB, 4GB, 8GB, 16GB and 32GB.
"Nominal Storage” always follows the Metric Measuring.
On metric measuring: 1 Kbyte=1000 bytes, 1 Megabyte= 1000 Kbyte, 1 Gigabyte= 1000 Megabyte.
“Actual Storage”
It’s the actual calculated number of bytes.
Stating the fact that: 1 Kbyte=1024 bytes, 1 Megabyte= 1024 Kbyte, 1 Gigabyte= 1024 Megabyte.
Now to simplify things:
“Actual Storage” = 0.9313 x "Nominal Storage”
Example:
2 Gigabytes "Nominal Storage” is ACTUALLY 1.8626 Gigabytes (2 x 0.9313 = 1.8626)
16 Gigabytes "Nominal Storage” is ACTUALLY 14.9008 Gigabytes (2 x 0.9313 = 14.9008)
Hope above helps

long story short
the 16 bg is correct however it is shared out between phone and external storage
take your 16gb, minus the space for the OS
on my sensation xl i have the following
phone storage is 8.89gb. thats nearly 9gb so we will call it 9
and internal is 3.7 so lets say 4
so thats 13gb all together and give 3gb for OS
thats 16GB