[Q] appreciate some info - Nexus S Q&A, Help & Troubleshooting

s 3G/4G signal and ram
1. *#*#3282#*#* enter msl to change port #'s to 0 and 0.0.0.0 so 3G is faster. Are there different instructions for ns4g. Port #'s under multimedia and says they are not set. So I'm asking if the hack for getting better 3G works on this phone ?
2. Since storage is built in, can it be allocated as virtual ram. I have seen this question before, but it always refers to a removable storage card. Don't really want to free up ram, just have more for usage.
I have searched, but maybe the question isn'tbeing asked correctly. If there is a point I'm missing, i would appreciate any info.
Was told first question doesn't work cause we don't use proxy port for 3G/4G on ns4g, would like to know what is uses and if there's a hack to get better signal
Rooted
Stock rom

This belongs in q and a or general. You can't write to sd for memory.
Sent from my Nexus S 4G using XDA Premium App

Paleryder said:
This belongs in q and a or general. You can't write to sd for memory.
Sent from my Nexus S 4G using XDA Premium App
Click to expand...
Click to collapse
Didn't see Q&A for Android Development
Can you elaborate on why you can't use storage memory and allocate as virtual ram. Just like on a PC, i would think because its apart of the phone and not removable.

Because ram in a PC is volatile, meaning its meant to be written to and rewritten to continousoy as long as there is volatage applied. The cathc is when that voltage goes away so does the information.
With SD storage like we are often dealing with on our phones it is nonvolatile memory meaning it can keep its data after the voltage is removed. The downside to this is that it is designed to be written to and stored as opposed to constantly being written to like RAM is. As a result, this type of memory only has a certain number of writes that it can have performned on a certain area before it goes bad and cannot be written to anymore. In essence it "goes bad".
Sent from my Nexus S 4G using XDA App

amistak said:
Because ram in a PC is volatile, meaning its meant to be written to and rewritten to continousoy as long as there is volatage applied. The cathc is when that voltage goes away so does the information.
With SD storage like we are often dealing with on our phones it is nonvolatile memory meaning it can keep its data after the voltage is removed. The downside to this is that it is designed to be written to and stored as opposed to constantly being written to like RAM is. As a result, this type of memory only has a certain number of writes that it can have performned on a certain area before it goes bad and cannot be written to anymore. In essence it "goes bad".
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
Thanks for the info
So i take it that when a PC uses the hardrive as virtual ram for a bigger cache, then its essentially doing the same. Explains alot more than what Eastwood was sayin.
Heard about removable SD cards going bad from wear, was hoping because this was permanent storage almost like a hardrive that it could simulate the the same way. Prolly means my harddrive is gonna go pretty soon on my PC then.

Was also asking because most of research i read was related to removable SD storage, and since my storage is built in and not removable through a slot like most phones, i was curious if the method would be the same. Guess not
amistak said:
Because ram in a PC is volatile, meaning its meant to be written to and rewritten to continousoy as long as there is volatage applied. The cathc is when that voltage goes away so does the information.
With SD storage like we are often dealing with on our phones it is nonvolatile memory meaning it can keep its data after the voltage is removed. The downside to this is that it is designed to be written to and stored as opposed to constantly being written to like RAM is. As a result, this type of memory only has a certain number of writes that it can have performned on a certain area before it goes bad and cannot be written to anymore. In essence it "goes bad".
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
Sent from my Nexus S 4G using XDA App

So the prl hack only works for some people, witch is not me. And trying to allocate memory as virtual ram for a larger cache is not going anywhere. From what i have read this is theoretically possible, but has only been done on removable SD cards. Witch wears the card down and is too slow for usability. This phone is way better than my old Evo 4G, but didn't have battery issues or signal issues on Evo 4G. Guess its back to Sprint, cause I'm still within my 30 days. Somebody stop me and tell me not too, that this is the better phone .
Sent from my Nexus S 4G using XDA App

Related

Samsung's Lag Fix

http://forum.xda-developers.com/showthread.php?t=762109
Can we replicate this on the Captivate? I've been playing around with my new Epic for a few days and it is AMAZINGLY fast. This is supposed to be the lag fix that Sammy employed on the Epic.
I knew it was just a matter of time until Samsung took action against the lag problem. I mean they wouldn't want their big, bad, and fast galaxy s line slowed to a screeching halt because of lag issues. I wouldn't be surprised if we see this in an update in the near future. With Samsungs track recored though they might end up waiting for Froyo to emplement it.
Sent from my SAMSUNG-SGH-I897 using XDA App
We have a nand lag fix already right? Wouldn't this give the same results? I thought the ext 2 internal storage lag fix was faster the the nand fix.
http://forum.xda-developers.com/showthread.php?t=737829&highlight=nand+lag+fix
I'm no dev but I think this is the same thing that's already been implemented by the community (for that matter, Samsung probably got the fix from the community )
From what most have gathered, samsung didn't fix the lag, they used different hardware that is faster. That will do no good for captivate and vibrant users.
l7777 said:
From what most have gathered, samsung didn't fix the lag, they used different hardware that is faster. That will do no good for captivate and vibrant users.
Click to expand...
Click to collapse
What the heck?
A) It uses the same hardware that matters anyway (granted LED, keyboard, etc is different).
B) Someone pulled the init.rc and proved what the OP is saying
C) You don't know what you're talking about
is there a good reference for the mapping of /dev/? or the whole file system in general? I went to see if busybox had a symlink for bash and much to my surprise there was no /bin. I'm new to android but a long time linux user and the differences are becoming readily apparent.
l7777 said:
From what most have gathered, samsung didn't fix the lag, they used different hardware that is faster. That will do no good for captivate and vibrant users.
Click to expand...
Click to collapse
I wouldn't go as far to say that. Everything is the same internally other than how the file system is setup, and in this case they are using the NAND (I believe).
From Boygeniusreport:
"We’re assuming the phone uses NAND Flash as the internal memory medium. On the Captivate if you navigate to Settings >SD Card and phones storage you see “External SD Card” and “Internal SD Card” listed. On the EPIC you see “External SD Card” and “Internal Phone storage.” We’ve reached out to Sprint for clarification and will update this article if they respond with a definitive answer."
Source: http://www.boygeniusreport.com/2010/08/18/your-epic-4g-questions-answered/
same hardware, different software...just minor things different
The Epic is missing the 16gb internal SD card... the SD card that Samsung has split into 2GB for apps and 14GB for /sdcard for the rest of the US Galaxy S devices (no idea how the EU phones are set up). As a result, it has far less space for apps, but it more than makes up for it in speed.
About the only thing that I think Samsung can do to improve speed on the rest of the Galaxy S phones is to either work like hell to come up with a better driver for the internal SD card, or to accept a massive limitation in app space and build in the original lag fix.
I'm hoping it's just a driver issue... when copying a 1GB file to and from my /sdcard using the USB mass storage mode, I sometimes see 10+ megs per second, and sometimes see >1 meg per second. This is with my phone sitting idle, nothing else going on at all (except for OS Monitor, so I can see what's going on). That leads me to believe that it's either a driver problem or the internal SD card is the world's crappiest. Seeing as everything else on the phone is very nice hardware, and seeing how the GPS and compass drivers have issues as well, I'm kinda (and maybe foolishly) thinking that it's probably a driver issue. We'll see.
It almost certainly is a driver issue. Formatting the internal SD with another filesystem provides a large boost in I/O performance. It's not as large as with the loopback hacks, which probably result in both subsystems buffering data, but it's enough to make using the device much more pleasant.
Sent from my SAMSUNG-SGH-I897 using XDA App
not sure if this has been covered already, but it looks like the Galaxy S phones use NAND for internal storage and not a flash card. the following link:
http://www.sprintdroids.com/forum/s...-galaxy-s-torn-down-extensively-detailed.html
will link a Korean site that tears down a Galaxy S device. here's the direct link to the translated Korean page:
http://translate.google.com/transla....com/News_List_View.php?nModeC=4&nSeq=1742568
andy2na said:
I wouldn't go as far to say that. Everything is the same internally other than how the file system is setup, and in this case they are using the NAND (I believe).
From Boygeniusreport:
"We’re assuming the phone uses NAND Flash as the internal memory medium. On the Captivate if you navigate to Settings >SD Card and phones storage you see “External SD Card” and “Internal SD Card” listed. On the EPIC you see “External SD Card” and “Internal Phone storage.” We’ve reached out to Sprint for clarification and will update this article if they respond with a definitive answer."
Source: http://www.boygeniusreport.com/2010/08/18/your-epic-4g-questions-answered/
Click to expand...
Click to collapse
on the Captivate, if you scroll down farther, past Internal and Externa SD Card, you will also see "Internal Phone Storage".
not sure if this has been covered already, but it looks like the Galaxy S phones use NAND for internal storage and not a flash card. the following link:
http://www.sprintdroids.com/forum/s...-galaxy-s-torn-down-extensively-detailed.html
will link a Korean site that tears down a Galaxy S device. here's the direct link to the translated Korean page:
http://translate.google.com/transla....com/News_List_View.php?nModeC=4&nSeq=1742568
Click to expand...
Click to collapse
The Captivate has both, as you can see quite clearly in the shell by using the mount command. Most if the partitions are segments of the NAND, using /dev/block/stlXX devices, but /data is /dev/block/mmcblk0p2, the second partition of the internal SD card. All are Samsung's proprietary RFS filesystem, which appears to perform poorly on the SD.
Sent from my SAMSUNG-SGH-I897 using XDA App
Unhelpful said:
The Captivate has both, as you can see quite clearly in the shell by using the mount command. Most if the partitions are segments of the NAND, using /dev/block/stlXX devices, but /data is /dev/block/mmcblk0p2, the second partition of the internal SD card. All are Samsung's proprietary RFS filesystem, which appears to perform poorly on the SD.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
pardon my ignorance, as i truly am ignorant in the subject, but how are logical names proof of physical hardware? could Samsung not have partitioned a NAND chip with different mount points and call them whatever they want? from the tear down pics, it seems that there would be no room for an internal SD card on the PCB. also, from reading around, it seems that all Galaxy S phones are pretty much the same hardware-wise, is this not true for the Captivate version?
again, i don't mean to come off antagonistic. i'm just searching for knowledge.
I just wish everyone would quit calling the system memory an "Internal SD card". There is no such thing. Samsung gave it this stupid name so the simpleton's of the world would realize it was data storage.
SD - Secure Digital is a form factor design. The phone has different kinds of flash memory and no one has yet to determine if the 14GB "internal SD" is a seperate chip from the total 16GB of internal storage.
Comparing this "Internal SD" to a real SD card is just dumb. An SD card is removable, of a certain physical size, has a write protection, and supports built in DRM - part of what Secure Digital means.
I am speculating too, but until someone can pinpoint the chips used on the captivate, we don't really know what this internal SD is made of.
-=HOLLYW00D=- said:
pardon my ignorance, as i truly am ignorant in the subject, but how are logical names proof of physical hardware? could Samsung not have partitioned a NAND chip with different mount points and call them whatever they want? from the tear down pics, it seems that there would be no room for an internal SD card on the PCB. also, from reading around, it seems that all Galaxy S phones are pretty much the same hardware-wise, is this not true for the Captivate version?
again, i don't mean to come off antagonistic. i'm just searching for knowledge.
Click to expand...
Click to collapse
I agree - SD is just NAND with DRM and some other features. I think Samsung just calls it this to separate internal OS/Application storage from user addressable storage. I would be there is one 16GB NAND chip as I have never heard of a 14GB chip. I bet they just partitioned the 16GB chip in different ways, but for some reason gave the 14GB chunk a slower FS partition by mistake.
Unhelpful said:
It almost certainly is a driver issue. Formatting the internal SD with another filesystem provides a large boost in I/O performance. It's not as large as with the loopback hacks, which probably result in both subsystems buffering data, but it's enough to make using the device much more pleasant.
Click to expand...
Click to collapse
Ah, good to know then. Thanks!
It is not only a logical name. While there may not be a removable card in a slot, the name suggests, and information in sysfs agrees, that the "internal SD" is accessed via an sd/mmc host controller. This means that many details about the flash are being hidden from the OS - it doesn't know what the erase block size of the flash is, it only sees a device with a certain number of blocks and a partition table at the beginning. Block remapping and wear levelling are hidden, which is why we can't use any of the linux filesystems for MTD devices. And for some reason, I'm not sure why, RFS performs much worse on an mmc device, or at least on this one, than it does on the OneNAND partitions. That it should matter seems a bit odd, as they are both block devices, but perhaps the OneNAND driver exposes some other information or interfaces via ioctl calls that are not present on the mmc device.
It is certainly possible for a filesystem to perform better on the internal SD than RFS does - this is easily demonstrated by formatting it with ext4 or nilfs2, and is also suggested by the improvement in lag that some seem to see with the leaked firmwares. In the future we may not care about alternate filesystems, because we get an rfs module that performs better on the internal sd.
Unhelpful said:
It is not only a logical name. While there may not be a removable card in a slot, the name suggests, and information in sysfs agrees, that the "internal SD" is accessed via an sd/mmc host controller.
Click to expand...
Click to collapse
sounds reasonable, thanks. but getting down to it, is it not at all possible that the internal "memory" is a physical NAND chip, albeit partitioned and interpreted logically however Samsung saw fit?
this may seem like a pointless debate, but perhaps if the community knew it was NAND for a fact, they could rewrite this or that to make things faster/better/etc..
here's a link that revers to the internal memory as NAND. not the source i'm looking for, but it's something:
http://www.66mobile.com/phones/samsung/samsung-galaxys.html
here's another spec sheet referencing NAND:
http://www.dropshippers.co.za/W32574411-Samsung-I9000/Documentation.html
here's an official Samsung site referencing NAND:
http://www.samsung.com/uk/consumer/...dex.idx?pagetype=prd_detail&tab=specification

[Q] Onboard 4 gigs sufficient for apps??

I'm in the process of deciding whether I get the Inspire or wait for the Infuse. I'm new to smart phones, but been reading a ton.
My question; is the 4 GB on the Inspire sufficient for the numerous apps I am likely to put on it? I think I've read about apps that let you place apps on the mSD. Is this even a concern I need to worry about?
Thanks for the help. Searched the forum and didn't see this addressed. Probably means it's a dumb question. I'm trying to get smart
Unless your going to have a couple hundred apps you shouldnt really worry to much.
Sent from skynet using XDA Premium Resistance App
I've downloaded plenty of apps and never even gotten close to using up the internal memory. I move what I can to the SD card, usually (it's not hard to do, and it's a feature built into the phone now).
Ditto, you'd have to work pretty hard to fill up that space, most programs are pretty small. But remember that many applications now support the A2SD function, so in the unlikely event that you start running out of room, moving them to your SD card is an option. I notice very little performance difference between apps on the card and apps run internally.

Internal Memory?

I was just wondering why my internal memory shows a total of only 2.58gb with 2.24 available when it is supposed to have a total of 8gb. Also does anyone know if the ability to access emmc is available or is it being worked on? Also a big thanks to all the developers that work on all these devices and share their hard work. Thanks guys
Sent from my ThunderBolt using XDA Premium App
jbeezybaby said:
I was just wondering why my internal memory shows a total of only 2.58gb with 2.24 available when it is supposed to have a total of 8gb. Also does anyone know if the ability to access emmc is available or is it being worked on? Also a big thanks to all the developers that work on all these devices and share their hard work. Thanks guys
Sent from my ThunderBolt using XDA Premium App
Click to expand...
Click to collapse
I second this question it's something I have wondered myself.
cstrife999 said:
I second this question it's something I have wondered myself.
Click to expand...
Click to collapse
It was like that even before I rooted. I noticed it but it didnt really phase me until recently. All my music/pics are on my card. I had to jump on HTCs site just to confirm that I was supposed to have 8gb and wasnt remembering it wrong..lol. But any insite to this would be helpful. Again thanks in advance for any help
I do believe it has 8gb but 3.2 gb of it is partitioned...
Sent from my ADR6400L using XDA App
I believe HTC partitioned it in a way that only 4GB of the 8GB eMMC is usable (the other 4GB is out of reach, it seems), and within that 4GB, you only get about 2.5GB or so user space, with the others reserved for the system.
And since it's one time only, we cannot reverse the effects of that partition.
Ya it is pretty ubsurd that you lose about 70% of your internal memory.
I do think it was smart to partition space for the system in excess of what is required, just to keep it stable.
Also, I imagine HTC had to put aside a hefty chunk of memory for HTC SENCE.
However, that seemed like way too much when I first encountered the problem myself.
So I e-mailed HTC who told me that the thunderbolt only has a 4GB eMMC under it's hood. That would make the numbers make sense because then the formatted space would be about 3.8 Gbs and that would mean only 1 gb was taken for the system.
why doesn't HTC or Verizon address the misprint claiming it has 8GB eMMC ?
that is a quesiton I can't answer.
nonnasmyladie said:
Ya it is pretty ubsurd that you lose about 70% of your internal memory.
I do think it was smart to partition space for the system in excess of what is required, just to keep it stable.
Also, I imagine HTC had to put aside a hefty chunk of memory for HTC SENCE.
However, that seemed like way too much when I first encountered the problem myself.
So I e-mailed HTC who told me that the thunderbolt only has a 4GB eMMC under it's hood. That would make the numbers make sense because then the formatted space would be about 3.8 Gbs and that would mean only 1 gb was taken for the system.
why doesn't HTC or Verizon address the misprint claiming it has 8GB eMMC ?
that is a quesiton I can't answer.
Click to expand...
Click to collapse
When I asked HTC about it, they said it has an 8GB eMMC formatted to make only about 4GB usable
I guess they lied to me. What's new.
Other people have been told that too.
Sent from my ADR6400L using XDA App
Thanks for the insight guys.
Sent from my ThunderBolt using XDA Premium App
This same question came up when the G2 came out and everyone was rasing holy hell about it.
Physically there is 8gb in the phone. However, if I remember correctly (you may need to Google it), the explaination was that because of the way Android uses memory, it is unable to use the extra memory properly. The only analogy that makes sense to me was like how in Windows, unless you set up your hard drive as NTFS, instead of FAT, you were unable to format a partition over 10mb.
Samsung got around it by showing the "extra" memory as another "partition" of sorts so the memory shows available.
So to make a long story short, the memory is there, but system limitations, along with some of the memory being used as backup cause you to only see the 4gbs.
At least that is the way I understand it. Maybe someone else may know more about it and can explain it better.
It has an 8G flash:
Code:
# fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Warning: deleting partitions after 60
Disk /dev/block/mmcblk0: 4487 MB, 4487905280 bytes
There's over 4G available as a flash device to the OS. I suspect the rest is where the radio code is stored, and is not visible to the Linux side.

usable internal memory

i am thinking of switching from att to tmobile for the sensation 4g. i currently use a desire and the usable internal memory after fresh reset isn't a lot. i just wanted to know how much usable internal memory do you get when you get it out of the box. since some programs still use the internal memory and programs that are transferrable to the sd card will still use a portion of internal memoyr. i'm not planning to root the device either, even though it's impossible right now.
It's different for a lot of devices. I was only getting about 100-125 megs of free ram out of the box. After I installed Launcher pro plus,I know get 175-210 megs free. Sense hogs everything up. Try a different launcher,you should get better results & a smoother running phone.
Sent from my HTC Sensation 4G using XDA Premium App
kevinf1990 said:
i am thinking of switching from att to tmobile for the sensation 4g. i currently use a desire and the usable internal memory after fresh reset isn't a lot. i just wanted to know how much usable internal memory do you get when you get it out of the box. since some programs still use the internal memory and programs that are transferrable to the sd card will still use a portion of internal memoyr. i'm not planning to root the device either, even though it's impossible right now.
Click to expand...
Click to collapse
The task manager isnt working right on the sensation,, if you go to settings>applications>running services then it should tell you how many memory is being used, I get 300 up free on mine.
Sent from my HTC Sensation 4G using XDA App

Phone finally fast

Hey Guys,
I finally got my phone to work at a decent speed. Here are the things I did:
1. Used Apps2SD to move the apps from internal storage to SD Card. Wondering why this helped? As far as I understand the apps are run in RAM and internal storage is used for storing data and apks etc. RAM is freed up by Android as and when needed but freeing up internal storage doesn't give android more RAM.
2. Use Autorun Manager to prevent some apps from starting up and remaining in memory. Now this I understand because this gives more RAM to android and avoids unnecessary swapping when applications are started up.
3. Used 'SD Booster' to increase sd cache size to 8192Kb. This gave some initial benefits but later on it became very slow as usual.
Bottom line is I am still puzzled by Android memory and SD card management. I am pretty sure though process swapping in and out of memory is what caused my phone to slow down. My Samsung Droid Charge is supposed to have 512MB of RAM but most memory managers show only 374MB and 2 GB of internal storage and most tools show only 1.2GB. Why would this be? Am I missing something or should I use a different tool to analyze my memory.
Not sure about RAM but usually when u buy a hard drive the bigger the hard drive the lower the actual number of gigs. Maybe it is actually 1.2GB
Sent from my SCH-I510 using xda app-developers app
1. This one must be a placebo effect because if anything moving apps to sd card will make the phone slower. Our internal memory has way higher i/o speeds (especially on ext4) than the measly class 2 sd.
2. This is usually not a good idea. The processes you "block" will actually still run but they will be insta-killed. They will keep trying to start up and will drain the battery.
Sent from my handheld computer using electromagnetic radiation.
JihadSquad said:
1. This one must be a placebo effect because if anything moving apps to sd card will make the phone slower. Our internal memory has way higher i/o speeds (especially on ext4) than the measly class 2 sd.
2. This is usually not a good idea. The processes you "block" will actually still run but they will be insta-killed. They will keep trying to start up and will drain the battery.
Sent from my handheld computer using electromagnetic radiation.
Click to expand...
Click to collapse
Thats what I thought. Im no guru, but out of all the reading Ive done, they have all said that moving apps from the sdcard to internal speeds up things.
Im looking at ways to speed up my wife's droid charge. Shes been complaining about it and finally gave me the go on rooting and maybee ROMing. I would like to stick to stock if possible so she wont run into any problems but if I have to I will install a custom rom. Any links?
Nope this is no placebo effect. The phone has become very fast. There are several posts that say that moving the apps to sd card speeds up the phone. In fact of all the things this is what sped up my phone the most. Why else would app2sd be so popular? Read #4 on http://www.talkandroid.com/guides/b...lean-up-and-speed-up-your-android-smartphone/ .
To further speed up my phone I am trying to overclock. My phone is stable at 1.2GHz but at 1.3 GHz it reboots after some time. To make it stable at 1.3GHz should I increase the voltage at that frequency?
salilsurendran said:
Nope this is no placebo effect. The phone has become very fast. There are several posts that say that moving the apps to sd card speeds up the phone. In fact of all the things this is what sped up my phone the most. Why else would app2sd be so popular? Read #4 on http://www.talkandroid.com/guides/b...lean-up-and-speed-up-your-android-smartphone/ .
To further speed up my phone I am trying to overclock. My phone is stable at 1.2GHz but at 1.3 GHz it reboots after some time. To make it stable at 1.3GHz should I increase the voltage at that frequency?
Click to expand...
Click to collapse
Read it again. That's only about getting extra app space on smaller-storage devices. They actually recommend against moving things you use frequently in your linked article.
I'm with the others. Any gains you're seeing from this are placebo. There's nothing inherently faster about external storage.
---------- Post added at 01:38 PM ---------- Previous post was at 01:34 PM ----------
salilsurendran said:
Hey Guys,
My Samsung Droid Charge is supposed to have 512MB of RAM but most memory managers show only 374MB and 2 GB of internal storage and most tools show only 1.2GB. Why would this be? Am I missing something or should I use a different tool to analyze my memory.
Click to expand...
Click to collapse
It has a total of 512MB RAM, and that is for everything, so the GPU and other such things have to take their share from the total pool. On the GB releases, that leaves us with 374MB. It's better than it used to be. On the Froyo releases, we only had 327MB to work with.
bubarub said:
Not sure about RAM but usually when u buy a hard drive the bigger the hard drive the lower the actual number of gigs. Maybe it is actually 1.2GB
Sent from my SCH-I510 using xda app-developers app
Click to expand...
Click to collapse
No, on a hard drive (or solid state drives or even SD/memory cards), what you buy is what you get. However, due to formatting, space reserved for backup/spare sectors, and what is considered a "gigabyte" to manufacturers vs consumers (1000 mb vs 1024 mb) you often end up with around 95% (probably off on that percentage) of the stated capacity. With RAM this is not the case, as that type of memory doesn't need formatting as its holding raw data with the computer making up its structure. And manufacturers of RAM are in agreement with consumers as to what a gig is.
Sent from my SCH-I510 using xda premium
bubarub said:
Not sure about RAM but usually when u buy a hard drive the bigger the hard drive the lower the actual number of gigs. Maybe it is actually 1.2GB
Sent from my SCH-I510 using xda app-developers app
Click to expand...
Click to collapse
This is the difference between a gigabyte and a gibibyte. Hard drives are usually advertised in gigabytes (literally 1 billion bytes), while most OSes use gibibytes (2^30 bytes, or 1,073,741,824 bytes), since they do everything in "base 2", or binary. So an advertised 10GB hard drive has 10 billion bytes. Once you format the drive, the OS reports size in gibibytes, so you end up with:
Code:
10,000,000,000 / 1,073,741,824 = ~9.31GiB
That's also why if you look on most hard drive packages, it says "formatted size may be different than advertised size" or something similar.
Just a random fact of the day. Feel free to ignore it.
On topic: I don't believe the giga/gibi (or in the case of phone RAM, mega/mebi) is the issue. 512MB converted to mebibytes is roughly 488MiB. I believe the Charge is a 512MB device with some of that memory reserved for OS/system-only purposes. I could be wrong on that, however, so if anyone could clarify that'd be great.
Edit: Could have sworn I read through all of the replies before replying myself. I guess I didn't because multiple people beat me on both points by a day. Sorry about that duplicate info.
Cilraaz, let's just say you compiled both answers into a single post...
Sent from my SCH-I510 using xda premium
The number one lesson I learned from buying this phone
Check the amount of run time memory before you buy a phone, especially if you have two companies like Verizon and Samsung loading bloatware. You were forced to root the phone and rid yourself of the bloatware, or not buy apps. I totally agree with the OP. He is 100% correct about the run time memory.
So I restored back to factory to get ready for another root. After the required Verizon and Samsung updates, hitting the clear memory button, I'm using 268MB of 373MB. Now I know the OS can swap, (because we love paging), but it really is ridiculous. I can't wait until March. Good luck everyone.
dbaps said:
Check the amount of run time memory before you buy a phone, especially if you have two companies like Verizon and Samsung loading bloatware. You were forced to root the phone and rid yourself of the bloatware, or not buy apps. I totally agree with the OP. He is 100% correct about the run time memory.
So I restored back to factory to get ready for another root. After the required Verizon and Samsung updates, hitting the clear memory button, I'm using 268MB of 373MB. Now I know the OS can swap, (because we love paging), but it really is ridiculous. I can't wait until March. Good luck everyone.
Click to expand...
Click to collapse
I couldn't understand what you are saying here. From what I understand you are saying that is that when you rooted your phone you had 512MB of memory but after you installed Verizon and Samsung updates it started saying you had 373MB. So is it that Samsung and Verizon updates are taking away about 147 MB of memory? What is going to happen in March?
salilsurendran said:
I couldn't understand what you are saying here. From what I understand you are saying that is that when you rooted your phone you had 512MB of memory but after you installed Verizon and Samsung updates it started saying you had 373MB. So is it that Samsung and Verizon updates are taking away about 147 MB of memory? What is going to happen in March?
Click to expand...
Click to collapse
No. Hardware wise the Charge has a total of 512 mb of RAM. The GPU and other hardware have to take from that pool, and the end result is that the Android OS has 373 MB of RAM to use. Verizon and Samsung bloatware and updates have no control over the hardware aspect, but the bloatware DOES utilize some ram while the phone is running (but does not take from that pool). March is probably when his upgrade is.
Sent from my SCH-I510 using xda premium
salilsurendran said:
Hey Guys,
I finally got my phone to work at a decent speed. Here are the things I did:
1. Used Apps2SD to move the apps from internal storage to SD Card. Wondering why this helped? As far as I understand the apps are run in RAM and internal storage is used for storing data and apks etc. RAM is freed up by Android as and when needed but freeing up internal storage doesn't give android more RAM.
2. Use Autorun Manager to prevent some apps from starting up and remaining in memory. Now this I understand because this gives more RAM to android and avoids unnecessary swapping when applications are started up.
3. Used 'SD Booster' to increase sd cache size to 8192Kb. This gave some initial benefits but later on it became very slow as usual.
Bottom line is I am still puzzled by Android memory and SD card management. I am pretty sure though process swapping in and out of memory is what caused my phone to slow down. My Samsung Droid Charge is supposed to have 512MB of RAM but most memory managers show only 374MB and 2 GB of internal storage and most tools show only 1.2GB. Why would this be? Am I missing something or should I use a different tool to analyze my memory.
Click to expand...
Click to collapse
What rom are you using? My son went swimming with his fascinate and I'm in the process of reviving my dc. I have compiled a few odds and ends and am mostly concerned about speed as well.
texbuck
texbuck said:
What rom are you using? My son went swimming with his fascinate and I'm in the process of reviving my dc. I have compiled a few odds and ends and am mostly concerned about speed as well.
texbuck
Click to expand...
Click to collapse
I am using Eclipse 1.4 with PBJ.
Ok so I can clearly see that my phone is becoming slow again. Not sure as to what it is related to. Though one thing that surprises me is that I overclocked the CPU to 1.2 GHz and set the governor as 'conservative' and sometimes even ' smartassv2' but it changes to 'ondemand' even though I never changed it to that value. Why is this happening?
salilsurendran said:
Ok so I can clearly see that my phone is becoming slow again. Not sure as to what it is related to. Though one thing that surprises me is that I overclocked the CPU to 1.2 GHz and set the governor as 'conservative' and sometimes even ' smartassv2' but it changes to 'ondemand' even though I never changed it to that value. Why is this happening?
Click to expand...
Click to collapse
Kernel? OC app?
Sent from my SCH-I510 using xda premium
salilsurendran said:
Ok so I can clearly see that my phone is becoming slow again. Not sure as to what it is related to. Though one thing that surprises me is that I overclocked the CPU to 1.2 GHz and set the governor as 'conservative' and sometimes even ' smartassv2' but it changes to 'ondemand' even though I never changed it to that value. Why is this happening?
Click to expand...
Click to collapse
Plugging the phone into a pc does that for some reason.
Sent from my handheld computer using electromagnetic radiation.
I have to agree that even though my phone was initially fast it slowed down considerably after some time. Frustrated I then backuped my phone using Titanium backup and installed Tweaked 2.2 Rom + PBJ. But this time I did the conversion to EXT4 and the phone has become super snappy and the fastest I have ever seen. However, I am not rejoicing right now because I have only installed some very necessary apps like navigation, yelp etc. Don't know if the phone will be come slow after I install more apps. On Seepu I can see for the first time my used memory is green and this probably is a major reason why the phone has speeded up. Another factor is the EXT4 conversion.
Infinity was known for slowing down over a short period of time. Tweaked 2.2 is quite a bit better. But running a Droid Charge for several days without rebooting it once in a while will cause it to slow down too. Just reboot when it starts slowing down. It should help.
Before I add any more apps I want to save this state of the phone so that I can go back to this if the performance degrades. What do I have to do for this? I used Titanium backup but I see that it saves app data and you have to install each individual app. What I want is to make one click and restore my phone back to the state it previously was. Should I do a nandroid backup

Categories

Resources