sorry for this question but i've just got this amazing phone but i've put some apps on the sd card and can't find the sd card on the phone ? even googled this but to no avail ! please help a newbie , thanks !
you mean the physical location of the SD Card? Its under the back cover. You need to remove the battery to get it out.
Also, apps are not stored on the SD card, but rather on the internal memory of the phone.
A couple of things. First you need to set up the phone for non market applications. This is done thru Menu>>settings>>applications and check the box that says Unknown Sources.
Next, if you use Astro or some other file manager, you can go to /sdcard and whatever folder you keep your apps in.
I use EOEAppsinstaller to do this. It searches the whole SD card to find any APK files. Works great.
QMAN101 said:
A couple of things. First you need to set up the phone for non market applications. This is done thru Menu>>settings>>applications and check the box that says Unknown Sources.
Next, if you use Astro or some other file manager, you can go to /sdcard and whatever folder you keep your apps in.
I use EOEAppsinstaller to do this. It searches the whole SD card to find any APK files. Works great.
Click to expand...
Click to collapse
thanks i'll try that !
It wasn't the physical finding of the card its how to access it to install apk files and a movie I installed !
does this means i can put applications on sd card without rooting my n1
audino said:
does this means i can put applications on sd card without rooting my n1
Click to expand...
Click to collapse
Yes and no. You can put apk's that you find on the net so you can put them on the SD card so you can install them but as for installing them so they run off the SD card that won't happen until you root the phone.
marra2 said:
thanks i'll try that !
It wasn't the physical finding of the card its how to access it to install apk files and a movie I installed !
Click to expand...
Click to collapse
+1 for Astro File Manager! It also has a built in apk installer AND task killer. I love multitasking apps.
your movie should appear in the Gallery
twiggy114 said:
Yes and no. You can put apk's that you find on the net so you can put them on the SD card so you can install them but as for installing them so they run off the SD card that won't happen until you root the phone.
Click to expand...
Click to collapse
ah oke im able to instal apps from sd card... i only have 162 free phone memory is this ok? i thought it comes with 512 memory and 512 ram?
audino said:
ah oke im able to instal apps from sd card... i only have 162 free phone memory is this ok? i thought
audino said:
ah oke im able to instal apps from sd card... i only have 162 free phone memory is this ok? i thought it comes with 512 memory and 512 ram?
Click to expand...
Click to collapse
another yes and no. Due to a bug both RAM AND ROM are limited to ~230MB ...all are waiting for the next update.
Took me 10 mins to type this in landscape mode due to keyboard bugs!
Click to expand...
Click to collapse
audino said:
ah oke im able to instal apps from sd card... i only have 162 free phone memory is this ok? i thought it comes with 512 memory and 512 ram?
Click to expand...
Click to collapse
The 512MB Flash ROM is shared between the OS and your installed apps. The amount left over for your installed apps after the system reserves space for the OS, scratch, recovery, and update partitions is around 190MB or so. Google mentioned that they are working on allowing us to store installed apps on the SD card so the size of this partition should not matter eventually.
The 512MB RAM is not used for storing the apps, it is used for running them and is a different set of memory. In 2.1 there is a kernel limitation that prevents them from using all 512MB just yet, but the next version of the Android Linux kernel will remove that restriction and we should see another 100 to 150 MB of memory available for use. That improvement won't have any impact on how many apps you can install, just on how many apps you can run at the same time and how much work they can do before they elbow other apps out of the way.
flarbear said:
The 512MB Flash ROM is shared between the OS and your installed apps. The amount left over for your installed apps after the system reserves space for the OS, scratch, recovery, and update partitions is around 190MB or so. Google mentioned that they are working on allowing us to store installed apps on the SD card so the size of this partition should not matter eventually.
The 512MB RAM is not used for storing the apps, it is used for running them and is a different set of memory. In 2.1 there is a kernel limitation that prevents them from using all 512MB just yet, but the next version of the Android Linux kernel will remove that restriction and we should see another 100 to 150 MB of memory available for use. That improvement won't have any impact on how many apps you can install, just on how many apps you can run at the same time and how much work they can do before they elbow other apps out of the way.
Click to expand...
Click to collapse
Sound cool if they really let us install on sd would be very nice and for me no more reasons to root my n1
audino said:
Sound cool if they really let us install on sd would be very nice and for me no more reasons to root my n1
Click to expand...
Click to collapse
Even more importantly - there would be no more disincentive for developers to start creating more interesting media-rich applications.
As it stands now, if you put a 10MB app on the market very few are going to be willing to waste that much space on their phone to download it. So, you wouldn't make much money on it. So, you are likely not going to bother developing it.
With relaxed storage restrictions will come nicer (looking, at least) apps...
Hi all,
There are a few updates/hotfixes for the Leo on the HTC website at the moment which I want to download and install. My question: As some of these files are quite large, one is 12mb, where would these files be installed, internal memory or SD card, or will I be given a choice as per cab installation?
Thx for any replies.
RoN_HD2 said:
Hi all,
There are a few updates/hotfixes for the Leo on the HTC website at the moment which I want to download and install. My question: As some of these files are quite large, one is 12mb, where would these files be installed, internal memory or SD card, or will I be given a choice as per cab installation?
Thx for any replies.
Click to expand...
Click to collapse
I surgest to install to Memory, it's safe.
douhua said:
I surgest to install to Memory, it's safe.
Click to expand...
Click to collapse
Thx for the reply.
I have about 60mb of free memory on my phone at the moment. The updates/hotfixes I've downloaded, 9 files in all, add up to about 32mb. I know I should have probably gradually downloaded and installed these files. Therefore I would prefer to install to SD card. Can anyone see any problems with this, or do these files NEED to be installed direct to the device?
Again thx for any replies.
RoN_HD2 said:
Thx for the reply.
I have about 60mb of free memory on my phone at the moment. The updates/hotfixes I've downloaded, 9 files in all, add up to about 32mb. I know I should have probably gradually downloaded and installed these files. Therefore I would prefer to install to SD card. Can anyone see any problems with this, or do these files NEED to be installed direct to the device?
Again thx for any replies.
Click to expand...
Click to collapse
these updates are not like cabs, and install into the ROM directly replacing previous file, so no extra storage is used up.
Not to mention you could just, take the stuff on your actual phone's memory and shift whatever files you have eating up the ridiculous amount of space the phone has on board to the SD card as well.
System files or updates shouldn't ever go on the SD card unless you're doing rom changing and that's a completely different beast. Reason being for me is that an SD card can mess up over time plus its nice to have reference to the files incase you need them again in the future.
Okay before anyone starts to flame or start saying "Oh God" to the screen, this isnt the typical "When are we going to get Android to boot from HD2" question.
I know we all boot Android from our SDCard, but I went looking to see if there was any google pages on why the sd card? Being that we have an HD2 and it has alot of space (My phone says 768mb free internal storage), would it slow Android and the experience down if we had the "Android" folder copied to our phone instead? I know currently it probably wouldnt work, but being that the avg Android folder is 230mb to 260mb thats more then enough space to put the folder in, and possibly change maybe the daily useage or app installations onto the sdcard. If this was just a general rule of thumb that it was decided to be put on an sdcard across the board because not all phone had the room then is there no way to change that now since most phones are coming out to have larger internal space opposed to older ones?
And again, would it be slower to run this way or not?
AngelDeath said:
Okay before anyone starts to flame or start saying "Oh God" to the screen, this isnt the typical "When are we going to get Android to boot from HD2" question.
I know we all boot Android from our SDCard, but I went looking to see if there was any google pages on why the sd card? Being that we have an HD2 and it has alot of space (My phone says 768mb free internal storage), would it slow Android and the experience down if we had the "Android" folder copied to our phone instead? I know currently it probably wouldnt work, but being that the avg Android folder is 230mb to 260mb thats more then enough space to put the folder in, and possibly change maybe the daily useage or app installations onto the sdcard. If this was just a general rule of thumb that it was decided to be put on an sdcard across the board because not all phone had the room then is there no way to change that now since most phones are coming out to have larger internal space opposed to older ones?
And again, would it be slower to run this way or not?
Click to expand...
Click to collapse
hi
Haret cannot currently read from NAND, its code reads and searches for Data IMG and Rootfs and kernal in SD ONLY .....
hence NAND is so very different from HARET.
well Magldr is what would do the trick
I'm assuming your talking about nand as to boot from the phone like as if you are powering it up and windows loads, Im not actually talking about that. I'm actually talking about how it currently loads, except, instead of placing the Android folder on the SDCard and running clrcad and haret, instead placing the folder into the root directory of the phone and running clrcad and haret from there, same exact way we are running it now, except changing the location of the folder from card to phone.
AngelDeath said:
I'm assuming your talking about nand as to boot from the phone like as if you are powering it up and windows loads, Im not actually talking about that. I'm actually talking about how it currently loads, except, instead of placing the Android folder on the SDCard and running clrcad and haret, instead placing the folder into the root directory of the phone and running clrcad and haret from there, same exact way we are running it now, except changing the location of the folder from card to phone.
Click to expand...
Click to collapse
hi
Well firstly NAND does not necessarly mean booting from start, NAND= Internal memory, in fact cotulla's MAGLDR can boot android of the SD straight from power up whilst having WIN MO on NAND.
So to answer your question again,
HARET CANNOT READ NAND (INTERNAL MEMORY), it always looks for SD for everything , in some cases RAM, as in the new RAM builds that are popping up by devs.
the code for HARET cannot handle NAND at the moment and i dont thing it will ever be implemented.
I'm neither a dev or a hacker, this is just what i ahve understood from reading, i'm open to corrections,
best regds
I have to admit, this idea is very cool.. If haret could "see" the nand memory after WinMo is loaded, then all you need is a WinMo rom stripped down to the maximum and Android folder burned in it (at least the system part). if if if i am not sure, if its technicaly impossible for haret to see the nand memory after booting WinMo or if its impossible at all..
greg17477 said:
I have to admit, this idea is very cool.. If haret could "see" the nand memory after WinMo is loaded, then all you need is a WinMo rom stripped down to the maximum and Android folder burned in it (at least the system part). if if if i am not sure, if its technicaly impossible for haret to see the nand memory after booting WinMo or if its impossible at all..
Click to expand...
Click to collapse
guys remeber HARET is a bootloader for LINUX, its crazy enough its helping us boot android from SD, I think the possible reason HARET is not designed for reading NAND is the potential damage it could do to SPL leading to a BRICK, now we dont want a brick do we ?
mally2 said:
guys remeber HARET is a bootloader for LINUX, its crazy enough its helping us boot android from SD, I think the possible reason HARET is not designed for reading NAND is the potential damage it could do to SPL leading to a BRICK, now we dont want a brick do we ?
Click to expand...
Click to collapse
never say never and expect the unexpected, thats what life teached me
phone wouldnt get bricked if you just read nand, but writing into it could do damage, i agree on this.
OK, so when I first read the OP, I thought he meant booting Haret from the phone's internal storage memory, not NAND.
Though the NAND Haret idea is really not bad, I couldn't see it corrupting the bootloader as long as it behaves the same way as it does from the sd. I mean, the phone is already booted WinMo, so HaRet and Android have no need to touch the bootloader, just as when running from sd. It would be more or less a startup.txt change/ rel_path = NAND/Android (not exact, but general idea). Seems alot different to me from MAGLDR, maybe there is just confusion about this
But if the NAND idea is not workable, wouldn't it be possible to run HaRet Android from the phone's internal storage memory, yielding a performance speed increase and less wear on the sd?
Clearly we couldn't do like I have now, a ton of builds with exceller, all running from internal storage, obviously we don't have 16gb internal. But what about just loading our daily driver from internal, and testing/less commonly builds from sd?
I like the idea because it could mean less wear on the sd, and possibly performance increase
BTW 300th post
Thats exactly what I meant, once WinMo is loaded, we normally go into the sd card thru file explorer and then go to android and then run clrcad and haret, winMo is already loaded and doesnt corrupt winmo, but if we could run the core system from the phones storage space, (Putting the android folder into the main directory, and then running clrcad and haret, this way the core system would load and any user installable files would just end up on the storage card, cause obviously we wouldnt be able to load all our apks into the phone (Some might, others like us go nuts).
But the concept is not a bad one, especially if there was a way when installing the apk's it asked for the location to add.
AngelDeath said:
Thats exactly what I meant, once WinMo is loaded, we normally go into the sd card thru file explorer and then go to android and then run clrcad and haret, winMo is already loaded and doesnt corrupt winmo, but if we could run the core system from the phones storage space, (Putting the android folder into the main directory, and then running clrcad and haret, this way the core system would load and any user installable files would just end up on the storage card, cause obviously we wouldnt be able to load all our apks into the phone (Some might, others like us go nuts).
But the concept is not a bad one, especially if there was a way when installing the apk's it asked for the location to add.
Click to expand...
Click to collapse
I would say that if HaRet was pointed to the correct place correspondingly, either NAND or storage would work as I previously mentioned. I am unsure about any performance gains to be had, but it would surely save on sd card wear.
People say that going from NAND would corrupt bootloader, but since WM is already booted using HaRet, there is no reason that the bootloader is touched, even if it is all stored to NAND. MagLDR is different, that is going for a cold-boot of Android, no WM involved at all. HaRet and MAGLDR work different and I think that if Haret was made to look for /Android in NAND, it could work just the same as if off of sdcard.
And booting from the phone's storage memory would be even safer, as no far-fetched idea of HaRet corrupting the bootloader is even conceivable, as NAND would never even be touched at all.
I honestly believe though that if a version of Haret was released that looked to NAND memory for /Android, that WM chefs could bake lite version WM ROMs with popular Android builds already built into NAND, maybe in the \Windows directory. The chef could even cook in a modified version of Exceller's Android loader which would look to \Windows for the Android folder.
Since Android development is so far along, and there are so many builds that are 100% or near 100% stable, I do think that going this route is a viable option, I mean there are already WM builds that will install an Android build to the sd card all by themselves after you boot them up the first time. This seems a natural progression of that concept to me.
Maybe somebody could contact Netripper, and ask him more about this idea, and see if he would be kind enough to build a HaRet version to look to NaND memory, and another to look to internal storage space, the rest could be done by the end user, as there are WM kitchens available, and most ppl here could make a .cab to install \Android to internal.
That's my $0.02
huggs said:
I would say that if HaRet was pointed to the correct place correspondingly, either NAND or storage would work as I previously mentioned. I am unsure about any performance gains to be had, but it would surely save on sd card wear.
People say that going from NAND would corrupt bootloader, but since WM is already booted using HaRet, there is no reason that the bootloader is touched, even if it is all stored to NAND. MagLDR is different, that is going for a cold-boot of Android, no WM involved at all. HaRet and MAGLDR work different and I think that if Haret was made to look for /Android in NAND, it could work just the same as if off of sdcard.
And booting from the phone's storage memory would be even safer, as no far-fetched idea of HaRet corrupting the bootloader is even conceivable, as NAND would never even be touched at all.
I honestly believe though that if a version of Haret was released that looked to NAND memory for /Android, that WM chefs could bake lite version WM ROMs with popular Android builds already built into NAND, maybe in the \Windows directory. The chef could even cook in a modified version of Exceller's Android loader which would look to \Windows for the Android folder.
Since Android development is so far along, and there are so many builds that are 100% or near 100% stable, I do think that going this route is a viable option, I mean there are already WM builds that will install an Android build to the sd card all by themselves after you boot them up the first time. This seems a natural progression of that concept to me.
Maybe somebody could contact Netripper, and ask him more about this idea, and see if he would be kind enough to build a HaRet version to look to NaND memory, and another to look to internal storage space, the rest could be done by the end user, as there are WM kitchens available, and most ppl here could make a .cab to install \Android to internal.
That's my $0.02
Click to expand...
Click to collapse
Very possible,
Haret needs to be modified for that,
not sure who can do it.
Guys as far as i know, on hd2 is nand memory the same as internal phone memory.There is no built in sd card. I am not 100% sure, but there is 512mb nand memory (internal memory). I mean, we install winmo roms into the nand. So if your winmo rom is about 200mb, you will be left with soemthing like 300mb internal phone memory. Correct me, if i am wrong..
cheers
greg17477 said:
Guys as far as i know, on hd2 is nand memory the same as internal phone memory.There is no built in sd card. I am not 100% sure, but there is 512mb nand memory (internal memory). I mean, we install winmo roms into the nand. So if your winmo rom is about 200mb, you will be left with soemthing like 300mb internal phone memory. Correct me, if i am wrong..
cheers
Click to expand...
Click to collapse
spot on
NAND = Internal memory
greg17477 said:
Guys as far as i know, on hd2 is nand memory the same as internal phone memory.There is no built in sd card. I am not 100% sure, but there is 512mb nand memory (internal memory). I mean, we install winmo roms into the nand. So if your winmo rom is about 200mb, you will be left with soemthing like 300mb internal phone memory. Correct me, if i am wrong..
cheers
Click to expand...
Click to collapse
Well true except the TMOUS, which is 1024 mb, so it should be plenty then to run Android this way right?
Even with just 300 left after WM ROM, Android could still be done conservatively, without much apps installed, or with some kind of a2sd functionality, Froyo has inbuilt app to sd functionality, albeit not as good as a2sd ext2 or ext3 setup.
Guys I think you are missing the point, If this was possible, viable or worth it, it would have probably already been tried and tested and released along time ago.
The fact that this hasnt been done already tells me that its been thought about and rejected for good reason.
PS. NAND ..IS.. Internal memory guys so the running loading of kernel and files from internel memory instead of nand is a moot point.
Here's a question for you guys thinking it *could* be possible to put Android on internal storage(NOT NAND) instead of SD...
What do you think will happen after your device creates the data.img and tries to place it in the Android folder on Internal Storage? I for one think my device(1024 TMOUS Leo) would run out of memory and throw error after error about internal storage being critically low until I did something about it.
To top it off, what about the 100 some odd folders that Android creates on the SD card now? Where are you going to put all of that on internal storage?
To sum it all up folks, until we're running from nand and have dedicated internal storage(W/O WM), it's not likely to EVER happen due to sheer lack of space, even if haret was reprogrammed to allow booting from internal storage.
dharvey4651 said:
Here's a question for you guys thinking it *could* be possible to put Android on internal storage(NOT NAND) instead of SD...
What do you think will happen after your device creates the data.img and tries to place it in the Android folder on Internal Storage? I for one think my device(1024 TMOUS Leo) would run out of memory and throw error after error about internal storage being critically low until I did something about it.
To top it off, what about the 100 some odd folders that Android creates on the SD card now? Where are you going to put all of that on internal storage?
To sum it all up folks, until we're running from nand and have dedicated internal storage(W/O WM), it's not likely to EVER happen due to sheer lack of space, even if haret was reprogrammed to allow booting from internal storage.
Click to expand...
Click to collapse
hmmm,
well in that case, kernel could be programed to create Data IMG on SD, if you have been following the Rhodium Nand Project , you will see what i mean, a few components are on NAND and a few on SD
dharvey4651 said:
Here's a question for you guys thinking it *could* be possible to put Android on internal storage(NOT NAND) instead of SD...
What do you think will happen after your device creates the data.img and tries to place it in the Android folder on Internal Storage? I for one think my device(1024 TMOUS Leo) would run out of memory and throw error after error about internal storage being critically low until I did something about it.
To top it off, what about the 100 some odd folders that Android creates on the SD card now? Where are you going to put all of that on internal storage?
To sum it all up folks, until we're running from nand and have dedicated internal storage(W/O WM), it's not likely to EVER happen due to sheer lack of space, even if haret was reprogrammed to allow booting from internal storage.
Click to expand...
Click to collapse
Its not about putting the whole Android folder into nand, but for example only the system partition, just like in the RAM builds. All data and user stuff goes to sd.
Btw what do you mean by "...*could* be possible to put Android on internal storage(NOT NAND)." ? nand is the internal storage (memory). Or you guys are using different terms do you mean by "nand" the reseverd space where roms are stored and by "internal storage" the free space left (still in nand)?
TheATHEiST said:
Guys I think you are missing the point, If this was possible, viable or worth it, it would have probably already been tried and tested and released along time ago.
The fact that this hasnt been done already tells me that its been thought about and rejected for good reason.
PS. NAND ..IS.. Internal memory guys so the running loading of kernel and files from internel memory instead of nand is a moot point.
Click to expand...
Click to collapse
Actually your part right, it was tested and released in the initial phases of the Rapheal (aka Fuze) and ran smoothly from what I read, yes there were hiccups, but that was due to the build being still in the alpha stages.
dharvey4651 said:
Here's a question for you guys thinking it *could* be possible to put Android on internal storage(NOT NAND) instead of SD...
What do you think will happen after your device creates the data.img and tries to place it in the Android folder on Internal Storage? I for one think my device(1024 TMOUS Leo) would run out of memory and throw error after error about internal storage being critically low until I did something about it.
To top it off, what about the 100 some odd folders that Android creates on the SD card now? Where are you going to put all of that on internal storage?
To sum it all up folks, until we're running from nand and have dedicated internal storage(W/O WM), it's not likely to EVER happen due to sheer lack of space, even if haret was reprogrammed to allow booting from internal storage.
Click to expand...
Click to collapse
This is where your part wrong as well. if you use a pre-set data.img file, yes for the most part you cant use anything larger then possibly 512mb on a TMous, 256 on others, definitely could not use the 1gb img file thats for sure, but the other part of this your missing is that if you dont put a pre-set data.img file, during the initial loading of android, android will create the file itself, and IF I am right the file will be sort of dynamic, dynamic in the sense it will expand as needed, I seriously doubt it shrinks. And on top of this you would then use the function a2sd, which in then would install your apk's to sd card. As of right now how much bigger is your 1gb data.img file that everyone added to their SDCards? Bet still the same size.
mally2 said:
hmmm,
well in that case, kernel could be programed to create Data IMG on SD, if you have been following the Rhodium Nand Project , you will see what i mean, a few components are on NAND and a few on SD
Click to expand...
Click to collapse
Actually after doing some reading, neither the kernel (if I read correctly) nor is haret.exe the cause of pointing the boot location. I did some searching (Mind you I am NOT a LINUX person), but reading some of the files, I am guessing that the key file which controls the loading of Android, is located in the "init" file in the rootfs.img file. I mounted this file in windows to look thru it and view files, and that file seems to have a major role in it, how it works I dont know yet.
To All, please I am not trying to cause a stir here, I am merely looking at possibilities, and unfortunately I cant test them out since I dont have a spare SDCard as of yet (Will ina couple of days, 32GB SDCard for $40, woohoo), and then I have nothing to loose to try, cant brick the phone, since winmo is the default loading OS anyway. One of the reason it might not have been put on the phone as I said, could be speed, I dont know how much faster internal phone storage would be opposed to sd, but another reason why could be cause then the installation would put folders on the root file system of the stroage card and make it messy. Also alot of people constantly flash new builds, this would also hamper your android install being on the phones storage. And remember our normal HD2 roms are between 225 and 250mb stock or custom, where lite versions or stripped down version would be considered better for taking up less space.
One thing to keep note, during all this, I have an HTC Aria (Liberty) as well that I just recently got as an upgrade to one of my ATT lines, and I checked the internal storage of that phone, its stock with ATT's build of Android, and it has ONLY 168mb of storage available, and it came with a 2gb sd card. Now think about that when saying that the files would get to big, obviously the HTC Aria doesnt have anywhere near the capacity of the HD2.
And again to anyone else, let's be clear, yes the phones storage is a NAND, but just to make clear, we aren't talking about doing a cold boot of android, I know how sometimes that can get confusing.
Sorry guys, yes internal storage is NAND memory, the reason I drew a distinction was to make a distinction between loading from internal storage and ROM space. I only meant to illustrate the difference between the two and demonstrate my opinion that both are possible. I think with further investigation and testing, advantages of booting this way will begin to emerge. For example we will be able to remove the sd card while Android runs, not a great benifit, but you get the idea. But yeah, I should have used the term 'ROM Space' instead of NAND, I only meant to show difference between the 2 places to boot from.
Sorry if i caused any confusion.
Sent from my... whatever
Hi there,
i know some answer about data.img such as here
But i still confused
what are the diffrences between 512mb & 1gb data ?
what's inside ?
thanks
Ronald
Mainly the amount of space available for installing programs etc.
oh ic..
so on my word , when i installed apps, it will installed there, is this right ? or ? sorry for this silly question
thanks
basically yeah that is where you install apps to (if not on "SD") and it has wifi settings, etc...
ronald_delgeano said:
Hi there,
i know some answer about data.img such as here
But i still confused
what are the diffrences between 512mb & 1gb data ?
what's inside ?
thanks
Ronald
Click to expand...
Click to collapse
Okay. I believe the most simple way to put it is like this:
On your stock HD2, you have a certain amount of memory on the device itself(512mb for unlocked HD2, 1024mb for TMOUS), this is where the OS is contained and also allows you space to install apps, store photos, music, etc...
The data.img that you either download from the thread or created by the Android build you're using is more or less exactly what is described above. It is "device memory" but contained in a single file so that it can be placed on the SD card.
Hope this clears things up for you.
EDIT:: Thread moved to Q&A forum.
Hello,
will the Android-made-data file expand during use?
cybercrash said:
Hello,
will the Android-made-data file expand during use?
Click to expand...
Click to collapse
No. There are guides in this forum on how to increase the size of one, rather than have to start again.
dharvey4651 said:
Okay. I believe the most simple way to put it is like this:
On your stock HD2, you have a certain amount of memory on the device itself(512mb for unlocked HD2, 1024mb for TMOUS), this is where the OS is contained and also allows you space to install apps, store photos, music, etc...
The data.img that you either download from the thread or created by the Android build you're using is more or less exactly what is described above. It is "device memory" but contained in a single file so that it can be placed on the SD card.
Hope this clears things up for you.
EDIT:: Thread moved to Q&A forum.
Click to expand...
Click to collapse
Clear enough
thanks
So I tried using WP7 On hd2.
But I didn't like it as much as Android. So I reverted back to android. But guess what I only have 200mb on SD Card instead of 16gb. (I should have expected this I suppose)
Can anyone tell me how to restore my SD Card to 16gb? I am sure there are others who are curious as well.
Thanks
Try formatting the card, windows, winmo or android, try em, it might work.
Get an adapter, shove it in a camera and format it
cos wp7 creates an unknown format partition. use a partitioning program, see if you can delete the partitions (there will be two, one 200meg fat and one unknown format) then reset a new FAT32 partition for the full size.
Be careful in disk management, delete from the wrong disk and its hello to up-all-night-reinstalling-your-PC, hehe.
I've used geparted live cd...worked fine. You have to delete partition and re- format as any filesystem you want.
TheATHEiST said:
Why's that? Because you didnt even bother to read the read me files like a tard??
Use some common sense ffs, Read info before doing anything like this.
It CLEARY states that WP7 creates partitions on your card and anybody with half a brain would know to re-format card after using a different OS especially one that creates partitions.
Click to expand...
Click to collapse
While I agree that the OP is at fault for clearly not reading anything and just flashing (I read instructions and used a different SD card when I tried WP7 - it was VERY clear!!!), I don't see why you feel the need to be so offensive to him. That's just plain out of order man. Stop just dissing people. If you don't have anything constructive to say then just don't say anything.
This is a friendly forum. Be friendly.
TheATHEiST said:
Why's that? Because you didnt even bother to read the read me files like a tard??
Use some common sense ffs, Read info before doing anything like this.
It CLEARY states that WP7 creates partitions on your card and anybody with half a brain would know to re-format card after using a different OS especially one that creates partitions.
Click to expand...
Click to collapse
Feel better about yourself after that?
Yup, I should have read about this before flashing but I had fun for a while and went back to Duttys Rom. However, I have 14gb of files and music on the card and a 200mb fat partition. Is there any way of at least retrieving the pictures and music before I reformat? Windows can only see the 200mb. Disk management shows the two partitions but won't let me delete the 200mb partition. Any suggestions?
I hope this guy doesn't treat his kids like that...."hey retard, go clean your room! It's the only way you'll learn"
The internet gives some people license to be morons unfortunately.
To the OP, I hope you get that fixed. If you find a way to fix it let us know which way worked for you in case we have to do the same thing to. I have a few SD cards but I don't want any of them to be rendered useless.
try using minitools partition wizard (home edition). delete both partitions so that each partition is displayed as a whole unpartitioned space and create a PRIMARY partition using fat32. your data was deleted when windows phone 7 was setting up for the first time. luckily i used another card but good luck
if you go bk to android leave a bit of space after when doing the primary fat32 and create a ext2 partition. its in the file system tab in the create partition bit
splinters69 said:
Yup, I should have read about this before flashing but I had fun for a while and went back to Duttys Rom. However, I have 14gb of files and music on the card and a 200mb fat partition. Is there any way of at least retrieving the pictures and music before I reformat? Windows can only see the 200mb. Disk management shows the two partitions but won't let me delete the 200mb partition. Any suggestions?
Click to expand...
Click to collapse
how about using usb storage in wp7 to transfer the files?
SH4YD33 said:
how about using usb storage in wp7 to transfer the files?
Click to expand...
Click to collapse
it wipes the card n formats it when win phone 7 first boots up.
Thanks everyone for their input. I managed to restore my SD Card. I am a happy android user. From my experience, I think android is far more stable than WP7. Android offers more versatility and customization. Again thanks.
Theres a fix for that just search
I couldn't find a way of saving the data so I lost it. Popping it in a camera formatted it perfectly. Won't be running wp7 again. Looks nice but too much hassle to get calendars etc.
To format the sd... put in the camera (mine for example is a nikon) and format it..
For me works well.
But I have another problem: in WP7 I have only some MB free.. so.. I can put in music if I have that little space?
My sd is 8GB...
dissa said:
To format the sd... put in the camera (mine for example is a nikon) and format it..
For me works well.
But I have another problem: in WP7 I have only some MB free.. so.. I can put in music if I have that little space?
My sd is 8GB...
Click to expand...
Click to collapse
Well so far I haven't been able to figure out the usb data storage method for wp7 if one even exists... so the only way you can put music and photos and other files onto wp7 is through zune.. if you try usb mass storage in magldr you will only see 200mb but through zune you can transfer files to your 8gb sd card capacity.
zup2sky said:
So I tried using WP7 On hd2.
But I didn't like it as much as Android. So I reverted back to android. But guess what I only have 200mb on SD Card instead of 16gb. (I should have expected this I suppose)
Can anyone tell me how to restore my SD Card to 16gb? I am sure there are others who are curious as well.
Thanks
Click to expand...
Click to collapse
to restore back yours 16 Gb, you must reformat your SD with SDformater Windows application.
lan78691 said:
Well so far I haven't been able to figure out the usb data storage method for wp7 if one even exists... so the only way you can put music and photos and other files onto wp7 is through zune.. if you try usb mass storage in magldr you will only see 200mb but through zune you can transfer files to your 8gb sd card capacity.
Click to expand...
Click to collapse
That is the problem. When I try to transfer just only a song Zune tells me that there is no enough space for the tranfer.
dissa said:
That is the problem. When I try to transfer just only a song Zune tells me that there is no enough space for the tranfer.
Click to expand...
Click to collapse
I had the same problem...
What you need to do is:
In Zune, go to 'Settings'. Then click on 'Phone'. Next, click on 'Reserved Space'.
Make the reserved space about 10%. This should give you about 6.5 Gb on an 8 Gig SD card. It also gives WP7 a bit of 'extra memory' to work with.
For a first release, this is an awesome piece of work. A few things don't work, but on the whole I'm impressed. I'm going to test it for a month to see how it performs.
The main functions work - Phone, text, e-mail, music, video. And nearly all of it is automatically set up. Correctly too.
Worked for me. Plenty of room for syncing via Zune.
Enjoy.......