Related
Hi, i am very new here and ilack some of the basic info. so i have couples of questions. thanks very much for your answers.
1. what is the internal memory of the htc hd2? and when you partition your sd to fat32 and ext3, will the internal memory be the sum of the ext3 and the phone internal storage?
2. when you want to flash your hd2 with a new rom. do you need to format both partitions of your sd card (fat32 and ext3)
3. when i tried the latest ultimate droid rom, i saw the author posted the rom and another thing called the layout (3.0.2.4_magldr_150M_partitionLayout_30M_cache). what does this do?
4. how do you make the phone to move or install apps in the ext3. and how do you back up those data and apps in the ext3?
and again, thanks guys for helping me out.
1 internal memory, do you mean what's available after a flash? 260 Meg or so with the small cm7 roms (typhoon for example)
No, the internal memory wont show the sum of internal plus ext BUT it will work as if it is. Say you install a 20meg program, internal mem goes down 20 but back up 20 after a restart.
2 no, when you perform the wipes through cwm it takes care of the ext partition and the .android folder on the fat32 for you.
Some apps may put data on the fat32, in which case you can delete those if you want or if you have isues.
3 the layout (clockworkmod, or cwm) sets up the various partitions on your nand (internal) memory, boot, system,cache,data. Without the layout there would be nowhere for the rom to flash into.
The main point of interest in cwm is the system partition size, big roms need big system partitions, sense roms for ex. need 250meg or more, typhoon needs 130. Flash a big rom to small layout fails, small rom on big layout wasted space.
4 you don't, if the rom says ap2sd enabled or words to that effect, it does it automatically. You can test this by loading up some apps then browsing the SD card on a Linux PC
When you run backups and such, it just does it, the phone has no idea that some of the info is on the SD, it treats it as internal.
samsamuel said:
Say you install a 20meg program, internal mem goes down 20 but back up 20 after a restart.
Click to expand...
Click to collapse
i dont understand why is that? so if the rom is apps2sd supported, it will automatically install apps to ext3. then it makes sense to me that the mem goes down, but then why it goes back up???
Example, 250meg internal plus 1gig ext partition.
internal memory shows as 250meg,, install 20 Meg app which goes to ext partition BUT the system displays internal mem as 230, , you reboot the phone and check again and internal memory shows as 250 again.
oh, thanks alot, i get it. but which backup solution is the best? and how does backup using clockworldmod work? does it make a backup file to sd card?
ljaypham said:
oh, thanks alot, i get it. but which backup solution is the best? and how does backup using clockworldmod work? does it make a backup file to sd card?
Click to expand...
Click to collapse
Hi,
It depends what you want to back up.CWM backup will take a snapshot of your entire ROM system,data,settings,everything.A bit like a ghost image of a drive on your PC.
This way, if you install a new ROM and there is a problem,or you don't like it,you can RESTORE your original ROM and everything is back the way it was before.
CWM backup saves to the sd card.
If you just want to backup data,use something like Titanium Backup.
Hello,
As the title says, I'm a new CM7 user (running verygreen's SDcard installer, using the 1.3 generic image, with nightly 87, no OC). This is running beautifully, except for one thing... I didn't use a big enough SDcard to start with and now I'm faced with looking for the right way to migrate to a larger card (or alternatively to make use of the NC's built-in eMMC in some fashion to augment the current SDcard).
Can someone tell me if the following approach will work? And is it the right/best way?
1. Use Win32Imager to make a full disk image of the current card (4GB).
2. Write the image to a new 8GB or 16GB card. At this point I should have a perfect copy except that there'll be wasted space on the card past the final partition.
3. Boot into a Linux recovery type LiveCD and use gparted to expand the final partition to use up the rest of the space.
4. Am I done? (crosses fingers?)
The goal of this move is to give myself some room to drop movies, music, etc. onto the /mnt/sdcard partition (which I believe is called /media by NC Stock 1.2?) Will what I described work?
Thanks in advance,
fuul4nook
P.S. One extra question, will the fact that my NC is a blue dot cause any problems with the idea? And if not, is there any way I can use the eMMC partitions while running CM7 from SDcard?
fuul4nook said:
Hello,
As the title says, I'm a new CM7 user (running verygreen's SDcard installer, using the 1.3 generic image, with nightly 87, no OC). This is running beautifully, except for one thing... I didn't use a big enough SDcard to start with and now I'm faced with looking for the right way to migrate to a larger card (or alternatively to make use of the NC's built-in eMMC in some fashion to augment the current SDcard).
Can someone tell me if the following approach will work? And is it the right/best way?
1. Use Win32Imager to make a full disk image of the current card (4GB).
2. Write the image to a new 8GB or 16GB card. At this point I should have a perfect copy except that there'll be wasted space on the card past the final partition.
3. Boot into a Linux recovery type LiveCD and use gparted to expand the final partition to use up the rest of the space.
4. Am I done? (crosses fingers?)
The goal of this move is to give myself some room to drop movies, music, etc. onto the /mnt/sdcard partition (which I believe is called /media by NC Stock 1.2?) Will what I described work?
Thanks in advance,
fuul4nook
P.S. One extra question, will the fact that my NC is a blue dot cause any problems with the idea? And if not, is there any way I can use the eMMC partitions while running CM7 from SDcard?
Click to expand...
Click to collapse
You should be able to do what you want but use Easeus Partition Manager to extend the 4th partition on the SD to get full use of the card. I don't know what you mean by "blue dot", but you can access 5 gb on the emmc directly through apps if it's music or video. You can also use File Expert or Root Explorer to store what you want on the emmc partition, which will then also be available when you boot into the stock NC rom.
I have been looking for something like this for a while. The flipout lacks internal memory and it soon becomes a problem if you want to have a good set of apps.
Here's what you'll need:
1. Rooted Flipout (I won't post instructions to this step, look for "Universal AndRoot")
2. Partitioned SD card (see below for instructions), depending on the method, you might need a phone with CWM to do this and ADB installed on your PC.
3. Download Link2SD from Market
So here are the steps:
1. Partition your SD card. There are many ways to do it. I will post two ways:
Use MiniTool Partition Wizard Home Edition
My PC didn't like this tool and I wasn't able to use it. However, it should be quite easy, you just need to put your card in a card reader and build two partitions with the following characteristic:
First partition will be your main card partition, should be of the whole card size minus the extended partition you want to create
Second partition should also be fat32 (link2sd didn't like ext2 nor ext3 on the flipout, it only worked with fat32)
Use CWM. I personally didn't want to install it on the Flipout, so I used a Samsung Epic 4G for the steps. You should be able to use any phone with CWM to do it, put your SD card in the phone with CWM and boot into recovery:
adb shell reboot recovery
parted /dev/block/mmcblk0 (open partition manager for SD card)
print (prints partition table)
Here you should have one partition table, starting at some point and ending at some point like 7969 if your card has 8GB. Take note of the End value as you'll need it.
rm 1 (deletes partition 1, this will erase all data on the SD card)
mkpartfs primary fat32 0 7425 (creates a new primary partition, the second number should be the value you took note of in the last step minus the size in MB of your desired extended partition).
mkpartfs primary fat32 7425 7937 (creates the new partition for applications, starting at the end of the last partition and ending on the max size of the card. In this case I used fat32 as I couldn't do it with ext3 nor ext2, link2sd didn't like this format on the flipout for some reason).
The partitions are created and you should be able to go to the next step.
3. Reboot your flipout with the partitioned SD card, make sure to have link2sd installed.
4. Open link2sd, it will take a while, ask for root permissions (always accept and make sure to have Remember checked).
5. It will ask for the partition type, select fat32. If you are asked to reboot your phone you have everything setup, otherway please post your problem.
6. Once rebooted, open link2sd again and go to settings and configure. I don't like having all applications automatically linked as widgets and this kind of apps can fail if they are on the SD, so I have this setting unchecked. However this is a personal decision.
7. To move an app to the card, hold your finger on it and when the menu appears, press link and confirm.
8. To move an app from the card to the phone, hold on it and press unlink, check everything and wait for the app to be returned.
Further Tips:
Avoid moving apps to the SD that are use widgets or that run all the time like: messenger apps, alarm clocks, climate widgets, etc. I tried one or two without any failure but I feel they could be less reliable this way.
Don't remove your SD card if the phone is turned on, now it has a partition that is used by the system, if you remove it you could have issues, I would only remove the card with the phone turned off completely and not boot without the card.
I made some tests connecting the USB cable to the PC and using the phone in storage mode, the PC could see the primary SD card partition and the phone could still work with apps on the second partition, so it seems to be stable in this sense.
If you need to switch to another card, you would have to setup the new card in the same way; I don't know yet if backing up the second partition and restoring it to the new card will work. If your data is critical use some SW like Titanium backup to back up the apps that are linked, remove them completely and restore when you have the new card setup.
So, this has worked for me like a charm, the phone really seems stable and I have so far like 150MB of apps on the SD card. No need to have a newer Android version, it seems very stable.
Disclaimer:
Any process that involves rooting your phone and partitioning can potentially cause data loss and/or bricking your phone. Do this only if you are 100% sure of what you're doing, I will take no responsibility for any data loss / damage caused by this process.
If you have any questions I will be glad to help.
Hi great post above
I rooted my phone and I partitioned my sd card into 2 partitions , both FAT32 primary 3.7GB and when i open link2sd and select either ext 2 or ext 3 I get an error message
"Mount scrip error
Mount scripe cannot be created.
mount: no such device
ext 2 may not be supported on your device. Try FAt32 on the second partition"
Has anyone come accross this problem before ?
Hi,
When you open link2sd,scroll down and select fat32. I tried formatting the second partition with ext2 and ext3 wit no luck. Fat32 is working just fine.
Regards
Hi Thanks a million that worked great
thanks
hi i tried wat u told but after some time link2sd is showing failure that "cannot link readonly" can u help me
Your guide works great. Finally I can have all apps I like to have installed at once.
mschmiedel said:
[*]If you need to switch to another card, you would have to setup the new card in the same way; I don't know yet if backing up the second partition and restoring it to the new card will work. If your data is critical use some SW like Titanium backup to back up the apps that are linked, remove them completely and restore when you have the new card setup.
[/list]
Click to expand...
Click to collapse
I can tell some experiences with backups.
Before I had blur stock rom with link2sd and changed to deblur central europe rom. After reinstalling link2sd all apps where still gone.
And even after restoring all user apps with titanium backup they were restored to phone memory. I had relink them with link2sd manually and to batch restore with titanium backup twice because it broke down in the middle because phone memory was full.
Unfortunately link2sd is no magically way to have them backed up apps and to be independent from the rom. Titanium backup is still needed but that is fine. Nothing seams broken after restore with TI and relink with link2sd.
lovdanie, it's strange, had no issues with the tested phone yet, I partitioned 500mb and it has already like 200-250MB of apps linked and is working great, no issues.
One thing that could have happened is that you removed the SD card. Are you sure the SD card hasn't been touched or formatted?
bagers, it's not really a magical solution, it's just a way to get more space on a phone that lacks internal memory...
Regards
Just for some info.. under windoze try the "MiniTool Partition Wizard Home Edition" makes partitions like charm..
Guys any one have links for disk partitioners? minitool is not a freeware as u have t buy it when you apply the partition. any one know a way roubnd this? please help
miniProBhashi,
That's why I always use CWM to partition the SD card. As I don't have it on the Bllur, I put the card on another phone I have with CWM and it always works... Maybe if you have a linux PC you could do the same thing...
Regards
Help
Hi, I just partitioned my SD card. When I open the Link2SD app, it did prompt me to select the file system of the SD card's second partion, however, after I select FAT32/FAT16, Link2SD could not gain root access, there's no pop-up of indicating me to select "Allow" on the Superuser Request. Now wot do I do. Please help, thank you...
Well, I would start checking the SuperUser app to see if there is some exception in there. If you don't have it, check out if your phone is rooted by installing some other app that requires root access.
If not, check the root method for your phone.
If it's the Motorola Flipout, download version 1.6.1 from this thread, install it and run it:
http://forum.xda-developers.com/showthread.php?t=747598
Regards
mschmiedel said:
Well, I would start checking the SuperUser app to see if there is some exception in there. If you don't have it, check out if your phone is rooted by installing some other app that requires root access.
If not, check the root method for your phone.
If it's the Motorola Flipout, download version 1.6.1 from this thread, install it and run it:
http://forum.xda-developers.com/showthread.php?t=747598
Regards
Click to expand...
Click to collapse
My phone is Galaxy ace, and superuser doesnt prompt anything on start-up.
Tried rooting manually, doesn't work as well
Hi,
I would try on a Galaxy Ace forum to check for the rooting process and validate if your phone is really rooted. When you are 100% sure you have root you can come back to this post and we can check if there's some other issue...
Regards
Flipout problem
Done all u told...
Then this problem came..
Mount script cannot be created.
mount: Invalid Argument
p0kjats said:
Done all u told...
Then this problem came..
Mount script cannot be created.
mount: Invalid Argument
Click to expand...
Click to collapse
Hi,
Have seen similar problems when using ext filesystems. Are you 100% sure that the secondary partition on the sd card is fat32? It really should work on the flipout without any issues.
Remember that you need:
* Rooted flipout
* Partitioned sd card (secondary partition must be fat32)
* Link2sd opened and allowed to use root permission
If you are sure you did everything stated above, we can look at it with more detail. What tool did you use to partition the sd card?
root permission
hi,
i have installed Link2SD from Market to my lg optimus p500 os,gingerbird2.3.3,when i stared to move app to sd it asks root permission.
so pls guid me to activate root permission in my device
drnags said:
hi,
i have installed Link2SD from Market to my lg optimus p500 os,gingerbird2.3.3,when i stared to move app to sd it asks root permission.
so pls guid me to activate root permission in my device
Click to expand...
Click to collapse
Hi,
It doesn't make much sense to use Link2SD if you're on Gingerbread as your OS natively can copy apps to the SD card (at least some of them). Just go to "Manage Applications", and select the app you want to copy, there should be an option to "Move to SD"...
If you still have some good reason to use Link2SD, you should first look in a forum for your specific device to find out how to obtain root (I cannot help because it varies for each device)... Once you have root access, I can help you out with this process.
Regards
miniProBhashi said:
Guys any one have links for disk partitioners? minitool is not a freeware as u have t buy it when you apply the partition. any one know a way roubnd this? please help
Click to expand...
Click to collapse
When I partitioned mine I used GParted Live. It's a Linux-based boot disk, but you don't really have to know anything about Linux to use it. Just download the .ISO and burn a CD, pop it in your PC and boot off it. Its free, graphical (not command line) and relatively easy to use. There is also an option there to set it up to boot live off a USB drive, but that's a bit more involved to set up.
gparted . sourceforge . net / livecd.php (sorry, it won't let me directly post links yet)
If you can burn a .ISO to a CD, you can probably figure it out. Just make sure you pay attention to which disk you are partitioning (look at the sizes) so you don't accidentally re-partition the hard drive in your PC.
EDIT: If there is anything you need to back up off the SD card, I would do that in Windows first, and then copy it back using Windows after. You CAN do this with GParted Live but there would be additional steps to mount / unmount the Windows partition on the PC that you want to copy to.
the bootstrapped recovery seems to be having a partitioning tool.
Maybe im wrong, haven't used it though
Hi,
First off if this is answered I am sorry.
I did a lot of searching and was unable to see the answer to this...
I am running CM7.1 off uSD. Install went well, and have no issues. That being said, I am unable to find out where on the card to sideload books. I have booted into CM7.1, turned on USB storage, and have 2 drives appear in win: MYNOOK and CM7 SDCARD. I used the size agnostic image, and it appears that there is only the single partition on the card, and in file explorer, it shows the correct card size for memory, but only the single partition.
The only folders appearing on the card are:
.android_secure
Android
LOST.DIR
I tried to manually copy the books, media, etc. folders into a My Files folder on this drive, without success.
There is no other partition to repartition (shouldn't have to do that with size agnostic?). I have no problem loading books into the MYNOOK book folder, which I assume is the internal device memory.
Here is my question. How/where do I sideload books to use the storage on the uSD card? Do I have to create the folders somewhere? If so where?
My goal is to utilize the storage available on the card, but be able to read the titles in the stock software. Is it possible to do this without rooting, or do I need to root for any reason to access the right folders on the card for storage?
THANK YOU ALL!!
klewlessnoob said:
I tried to manually copy the books, media, etc. folders into a My Files folder on this drive, without success.
Click to expand...
Click to collapse
In what way was it not successful? Did the files copy and just can't find them with a reader? If so which reader?
The book I transferred over was not found in the stock software when I opened my library. Is there somewhere specific I am supposed to place it on the card for the Nook to see it? Thanks!
For the stock reader, I think you must use the 1gb area of the internal memory drive, which shows up as a separate drive on your PC when you plug it into the computer. When you are in CM7 and connect to the pc, cancel when it tries to install a device for the NC. Check the notifications on the NC, you need to click a button to enable copying files from your pc, and take care to properly safely remove/eject before disabling that and disconnecting the cable from your pc. Better to get a separate reader and install it from the market (e.g., Cool Reader). You can also install the Nook app from the market, but then books need to go within (possibly in a specific subdir) of the "Nook" folder on SDCARD.
So there is no way to use the card memory to store books if I want to use the stock reader??
Should there have been a "NOOK" folder created on the SD card as part of the CM7 process? Is that a file that the user needs to create? If so, does it go in the same partition as the CM7, as that is the only partition my machine is able to see?
thanks again
Hopefully you'll get more input on this, but I think the point of keeping the Nook stock available (aside from not voiding your warranty) relates to use of B&N books. However you can eject your CM sd card and use another sd card if you want more space for user media for use with the stock app. I thought the media drive was the 1gb area, but now I'm not so sure because on mine the MYNOOK disk is much smaller.
When you are in the stock firmware... you are seeing the boot partition of the uSD...
You can write the boot partition... resize it... then run the installer...
I have done it in the past... set up a 2GB boot partition... then setup the ROM on uSD. You then have a 2GB partition you can use when in stock.
Thanks for the info. I am a bit confused by your suggestion, can you please offer a bit more?
By writing the boot partition, then resizing it, does that mean I can resize now, after I have already set everything up? If so, what do you mean by the installer? Or do you mean I have to wipe the card and start over? If that is the case (start over) do you mean wipe the card, create a small partition for the boot to install on? Would that requre the use of an image that is not size agnostic?
Either way, how do I get the file structure in place on the non boot partition for the nook to see files that are saved there?
Thanks again for any help you can provide!
I have never had luck resizing it after it has been booted in the Nook and all the partitions created...
I have written the size agnostic image to the card... resized the only partition created at that point... then put the ROM on it and booted it in the nook so the installer script (size agnostic recovery) can do the partitioning and install the ROM.
For the question of getting the file structure... I'd have to ask how you wrote the files on the uSD... were you CM or stock?
I had always planned on running cm from the card, so when I wrote the files to the card, I was stock.
If I follow what you are saying, then steps for me to try at this point would be:
1. Reformat card
2. Write the disk image to the card
3. Shrink the single partition on the card (where the image is)
4. Add the CM ROM to same partition as the image
5. Install card and boot device
If this sounds right, I have 2 questions.
What size should the partition be for the image and CM ROM, maybe 2GB?
Will the Nook "see" the non-CM partition and create the file structure for saving files on the 2nd partition at some point? In my searches I saw that in early versions, there was a requirement that the 4th partition on the card be expanded to use for storage, won't I only have 2 at this point?
Thanks again so much for the help!
When you write the image to the card... it will only be about 114 MB.... you will probably want to increase the size to avoid any possible size issues later (with ROM's getting larger)
If you plan to use the stock nook ROM as well as CM7... you will probably want 2 GB boot partition... otherwise if you plan to only run CM7 you probably only want about 250 MB.
You can modify vold.fstab on the stock ROM to use partition 4 of the SD for its SD use... then you could avoid the 2 GB boot partition.
What happens when you use VG's SASD... the boot image is about 114 MB... when you boot it in the nook it creates partitions 2, 3 and 4... 2 and 3 are ext3 partitions, partition 4 is fat... partition 4 is the one set for sdcard in the ROM booted from SD...
This is why you can modify stock vold.fstab to point to partition 4... then both ROM's will be putting stuff on the same partition for "SD Card"
I think I follow that, but my issue is that currently I am unable to see partition 2,3 or 4 which I think is part of my problem.
When I set up the card, I used the SASD method, and all I can see in both win explorer and partition software is the single partition on the card. Should there also be partitions 2,3, and 4? Do I have to do something to make those partitions viewable?
I am not comfortable enough with my skill level to attempt to modify the stock vold.fstab file on the device, and was hopeful that by properly setting up the card, I would be able to keep stock as is, and use the card to multipurpose, ie run cm7 on part and use the remaining space on card to store books to be read in stock firmware. I am still hoping to do that....thanks
As far as only seeing partition 1.... that is a limitation of Windows.
By following the advice pertaining to starting over and increasing the size of the Boot partition immediately after writing the image... before doing anything else... you can provide more space for the stock ROM to use on the SD... it will use partiton 1 (the boot partition) without the other modifications to vold.fstab
ok, confused again
If I start over, write image, then resize that partition with the image, am I going to use the "rest" of the card, NOT in that partition to use with storage? OR am I going to resize the partition with the image to be big enough to use as the partition to put books on?
If it is the former, don't I again run into the problem of how to find the other partitions, or will I create them when resize the first partition after writing the image?
Thank you!
You will only ever see the first partition of the sd card when booting from the stock OS. Also with the card inserted in a usb flash card reader on Windows you can only mount the first partition as a drive letter. But you can see and resize partitions with contiguous unallocated space using MiniTools Partition Wizard.
OK thats good to know. Do you know if the SASD install should have created other partitions when I installed to the card? The reason I ask is that even in Partition Wizard, I am still only able to see the 1 large partition with everything in it.
If I start over again, will I need to use the wizard to create partitions first, then write the image to the resized 2 GB first partition, or should I write image to card, resize the first partition? If the latter, will resizing the first partition autmatically force the other partitions to be seen? I am not sure of this option, as I can't see where in the process the other partitions are created? Is this part of the process when CM7 boots?
Thanks!
Write the image. Safely remove from pc. Reinsert to pc. Use minitool partition to resize the (only, at that point) partition to the size you want. Use Apply in minitool software. Quit minitool and resume with the card setup.
does the minitool at that point (resizing) create the other partitions, or will the card setup do that? Do I have to do anything else to the other partitions to make them visable to the stock nook so that they can be used to access books while in stock os?
The card setup will create the other partitions. The stock os is never going to see anything but the 1st partition. You would need a terminal emulator or rooted file explorer installed in the stock os in order to mount another partition.
If that is the case, that stock os will never see anything other than the 1st partition, then there really is no way to accomplish what I am trying to do, correct?
In other words, put CM7 on the card, then when I want to use stock, boot into stock and have the reader find books saved on the card?
I'm trying to understand the most convenient way to make a copy of an SD card that has an EXT partition on it. This would need to be done anytime you upgrade from a smaller to a larger SD card, so I have to believe a number of people on these forums have dealt with it.
This is what I'm expecting to be done... please confirm if it's correct:
Make a nandroid backup, stored on the old SD card
Copy the nandroid backup to PC
Install new SD card and partition it accordingly
Copy nandroid backup to new SD card
Perform a nandroid restore
At this point, everything should be as it was, with the larger SD card. Correct? I've also noticed an alternative that would probably work, that being a partition management program like EaseUS.
My 32Gb SD card arrived so I downloaded Mini-Partition to set it up. Then when I went to copy the EXT3 partition from my 8Gb SD card, the option wasn't possible. Apparently I can't copy it into a larger EXT3 space, only unallocated space. So, I removed the target EXT3 partition, making it unallocated, and then tried to copy and resize. Apparently the tool won't let you resize an existing EXT3 partition. I installed EaseUS to try this operation and encountered the same thing.
From what I've just experienced, I'm now thinking that if I try to restore a nandroid backup onto my new card, it will override the newly minted EXT3 partition with the smaller EXT3 partition.
Searching around turned up a lot of Ubuntu/Linux information, requiring one to boot up in those operating systems and execute a long series of commands to enlarge the EXT3 partition. I'd rather not go down that path right now. Is there some easier way of doing this? If not... then I'm thinking what I need to do is move as many apps having data I need to my phone, then just opt not to restore the EXT3 partition and go back to manually move apps to the EXT3 partition again.
* bump * .... anyone?
cytherian said:
* bump * .... anyone?
Click to expand...
Click to collapse
What rom are you running?
Shelnutt2 said:
What rom are you running?
Click to expand...
Click to collapse
Presently running CM7.2, which supports EXT3. I'm just not getting how I can manage the EXT3 partition. When I switch to a new ROM and wipe the system, then all apps installed on the EXT3 partition would be deleted, correct?
So, what this ultimately means is that each and every time I switch ROMs, the EXT3 partition must be wiped and applications manually moved back there. It's annoying, but I haven't found any other way around this.