Database Develop

sd space question

I have a 4 gig sd card with it partioned ext2,ext3, and a linux swap. To be honest I don't know really what that means exactly, just followed the tutoriul to have my apps to go to my sd card. When I go to sd storage info it says.
Total space- 3,255mb Available space 1,875 mb.
Under Sd card secondary it says Total space- 457mb Available space- 292mb
For Internal phone storage it says 78mb available.
My question is where are my apps actually going? And where does my other stuff such as music, movies and other files go? From what i am guessing I have 1875mb for files and 292mb for apps. Correct? Thanx in advance for explaining this too me.

It should be fat32, ext3, linux-swap. 78 megs sounds right for apps2sd. Your apps go to ext3 along with your cache, movies and other files you can browse on your phone go to your fat32which is your normal storage and swap is a location where your phone puts operating memory to hold more processes in the background(helps out you ram)

badaphooko01 said:
To be honest I don't know really what that means exactly
Click to expand...
Click to collapse
This is a warning flag that you will probably brick or otherwise disable your phone in the future.
Nothing in the dev subforum should be performed until you fully understand how it works.

jashsu said:
This is a warning flag that you will probably brick or otherwise disable your phone in the future.
Nothing in the dev subforum should be performed until you fully understand how it works.
Click to expand...
Click to collapse
I doubt everybody here knows exactly every technical detail and aspect about their phones. In addition I knew I was partioning my sd card just wanted to understand where all my files were going. I have successfully rooted my phone the old fashion way and installed numerous roms and themes after many hours of reading and following directions in these forums. I'm sorry i am not expert in linux or coding. All I asked was for some information of the subject, if you can't help then don't post. Thanks gridlock for your answer.

You are welcome but I must defend jashsu, you have only been a member since last month and made a few posts, he was just staying on the side of caution because there are a lot of people who just dive in without knowing what they are doing and no offense but your ? Was a common type of ? That a noob who did not have much knowledge would ask

badaphooko01 said:
if you can't help then don't post.
Click to expand...
Click to collapse
I tried to help, you weren't receptive of it. Maybe a second time with some added emphasis will drive the point home?
Nothing in the dev subforum should be performed until you fully understand how it works.
Are there people in the dev forum who can/should do things that they don't fully understand? Of course; they are the hackers and experimenters who are not afraid of bricking their devices. I assume (perhaps wrongly?) from your comment "I don't know really what that means exactly, just followed the tutoriul" that you are not one of those people. I'd be happy to be proven wrong.
I stand by what I wrote.
Edit: by the way the asking of questions (although searching would be good too) is part of the process of learning and therefore understanding. I was not at all trying to discourage you from asking the question, I was just pointing out the danger of proceeding with dev modifications without proper understanding.

78mb?? your lucky I only got 33mb! and I got cyanogens rom with automatic apps2sd!
where do you guys reckon my space has gone?

Did you wipe before you flash cyanogen, right now on 4.04 I have 64mb internal with running the danger spl, that does change internal memory

[TUT]MIMO Ext 4 Kernel on Vibrant

It seems the firmware after the models xjm1 and xjm2 are bricking phones on reverting back to US firmware. Thought it was my phone. So im getting rid of this thread.

previous post edited...sorry I read wrong......

Nope, just wanted to show off my homescreen in case anyone was wondering compatibility issues with applications that everyone is familiar with. Those were just some of the main applications I know a wide audience tend to use, so I picked them to display.

damn,.. you already answered to my stupid question.... sorry for wasting your time...anyways I've got few new questions!
After MIMO Ext 4 procedure is done...
1) What happens if you take out the external memory card after booting...
2) What happans if you lose the external memory card? Is the phone considered bricked then?
3) How do I reverse the MIMO Ext 4? (get rid of MIMO Ext4)
Anyways great info!!! I might actually try JM2 installation!!

andeeroid said:
damn,.. you already answered to my stupid question.... sorry for wasting your time...anyways I've got few new questions!
After MIMO Ext 4 procedure is done...
1) What happens if you take out the external memory card after booting...
2) What happans if you lose the external memory card? Is the phone considered bricked then?
3) How do I reverse the MIMO Ext 4? (get rid of MIMO Ext4)
Anyways great info!!! I might actually try JM2 installation!!
Click to expand...
Click to collapse
1. Since your application data is now stored and ran from the sd card, your applications will go wonky, and any applications you try to install or reopen that have been close will not open.
2. No, if you lost the sd card, you can simply format another one, or use ROM manager and the clockwork recovery to reinstall your stock rom.
3. Rom manager or reflash original firmware with ODIN. But I recommend using Clockwork recovery to reinstall a nandroid backup found in the development section here, or an update.zip. As these methods are less intrusive an will give you less problems.

yay!! now I know and I dont' have to shiver in fear bricking my phone trying MIMO Ext4 !!!!!!!!!
I appreciate your swift replies !! I'll probably try this when I get some free time !!

If I could track down a i897 phone file, I'd be all over this on my Captivate.

Croak said:
If I could track down a i897 phone file, I'd be all over this on my Captivate.
Click to expand...
Click to collapse
Yeah, I had captivate in my possession yesterday, and this exact method did not work for it. Of course it might would if I could of found the exact firmware for the captivate split into the three odin files, rather than the all in one click exe. But i've returned it since then, so I won't be able to look into that anymore.

I used a program called Universal Extractor to bust open that one-click file, but all it could extract were the non-binary files inside, about 300kb of .xml, .txt and script files, in the META-INF and system directory.

I don't get it.... Why is this a goid thing to move all of your data to your sd... ?

Have you figured out why you don't have data service?
This is good write up. There are some captivate owners looking to do the same. But we don't have the firmware package u have on the vibrant. I am sure someone will come up with it. However, No DATA is a problem. I need data service. I tether alot. I pretty much depend on it.

PJcastaldo said:
I don't get it.... Why is this a goid thing to move all of your data to your sd... ?
Click to expand...
Click to collapse
Its for the lag fix, but doesn't have the space limitations that the nand partition does.
Sent from my SGH-T959

tissimo said:
Its for the lag fix, but doesn't have the space limitations that the nand partition does.
Sent from my SGH-T959
Click to expand...
Click to collapse
Really, an ext part on the sd card is faster than the internal memory? K.. I know alot of people have bad lagg, but I havnt seen it. Buy thanx fot lettin me know.

PJcastaldo said:
Really, an ext part on the sd card is faster than the internal memory? K.. I know alot of people have bad lagg, but I havnt seen it. Buy thanx fot lettin me know.
Click to expand...
Click to collapse
Its due to the I/O of the internal memory. IIIRC the internal is limited to sequential read/writes, but I guess the external isn't (and neither is nand).

Thanks for this .

CWR, EMMC ????

Hi, I'm a bit stupid..
What does CWR and eMMC means ?
eMMC is that the internal memory of the NookColor ?
Do you mean we can now install Android directly inside the nc and no longer booting on the sd card ?

glayourt said:
Hi, I'm a bit stupid..
What does CWR and eMMC means ?
eMMC is that the internal memory of the NookColor ?
Do you mean we can now install Android directly inside the nc and no longer booting on the sd card ?
Click to expand...
Click to collapse
This should be posted in the General section.
CWR = Clockwork Recovery
eMMC is the internal memory of the NC. Yes, there are versions of Froyo and HC that you can flash directly to emmc.

Sorry for the bad placement, can it be moved to the correct section ?
and what is Clockwork Recovery ?
the aim of this is ???

glayourt said:
Sorry for the bad placement, can it be moved to the correct section ?
and what is Clockwork Recovery ?
the aim of this is ???
Click to expand...
Click to collapse
Instead of having to DD images you can easily just update the eMMC through a zip file. It also makes it a bit easier to recover from bad images for some people

CWR is (in my opinion) essential for those who regularly root and flash. Like the previous poster said, it allows you to flash kernals, ROMS, etc., easily because there is a UI that is easy to navigate. It also allows you to create a nandroid (backup), which would make it easy for you to restore an image if you ever fudge anything up, which is bound to happen. There's a lot more you can do in CWR. It's definitely a must have.

eyecrispy said:
CWR is (in my opinion) essential for those who regularly root and flash. It's definitely a must have.
Click to expand...
Click to collapse
Saved my bacon more than once, agree a must have for anyone rooting and flashing.
Mike

Help, several NOOB questions

THANK YOU IN ADVANCE FOR ANY HELP! I'm dead new with android and just got a Nook HD+ 32gb (groupon deal $130)
anyway, I've done a ton of reading on here and watched a bunch of youtube vids- i don't know if people use overlapping terminology that means the same things or what.. and also seems like theres a lot of opinions in the forums.
I want basically the full android experience and root access- like i said, never used any android, but i like toying around with these things. BUT i also really want a fully stable platform- don't want constant crashing or it reseting on me.
questions i have-
1)the CWM is the "program" (don't know the correct terminology) that basically gives me the access to back up and install new roms, root, etc? TWRP does the same thing- but i understand you don't use that?
2)If i have a BRAND NEW nook HD+ do i need to back it up before messing with it OR are the "stock rom" zips you provided just that?
2) with the SD card image, do i need to put a specific image on the specified sd card. i.e. 4gb SD gets a 4gb image? or is the image universal to whatever size SD card i get?
2a) What problems am i going to run into using my mac to make the SD card, if any? what program do i need to use?
4) when you back up through CWM where does it save it? to the SD card?
4a) this is where i was confused about the image, reading into some of the posts it led me to think the image file took up the entirety of the
SD card.
4b)So in the future i could just boot from the SD card and would have the option to flash the stock rom back on the HD+ if desired? and/or
go back to CM?
5) what is DUALBOOTING? and NANDROID? how do they tie into CWM and CM10. very confused about this.
6) any disadvantage to flashing the EMMC vs booting from SD card every time? I THINK i want to flash the emmc, i don't want to be tied to booting from the SD card everytime- if I'm understanding that correctly.
7)what is this "trim" lag problem? couldn't really figure out what people were talking about.
thanks a ton for any help you can give me- I'm sure you receive a lot of questions!
-Sonny

santinod15 said:
THANK YOU IN ADVANCE FOR ANY HELP! I'm dead new with android and just got a Nook HD+ 32gb (groupon deal $130)
anyway, I've done a ton of reading on here and watched a bunch of youtube vids- i don't know if people use overlapping terminology that means the same things or what.. and also seems like theres a lot of opinions in the forums.
I want basically the full android experience and root access- like i said, never used any android, but i like toying around with these things. BUT i also really want a fully stable platform- don't want constant crashing or it reseting on me.
questions i have-
1)the CWM is the "program" (don't know the correct terminology) that basically gives me the access to back up and install new roms, root, etc? TWRP does the same thing- but i understand you don't use that?
Click to expand...
Click to collapse
CWM (ClockworkMod) is a recovery program that allows you to do just what you said. TWRP is also a recovery, but uses the touch screen instead of hardware keys to control it.
2)If i have a BRAND NEW nook HD+ do i need to back it up before messing with it OR are the "stock rom" zips you provided just that?
Click to expand...
Click to collapse
You can either use the CWM backup tool to return your device to stock (including any data you have already created, like registration) or the plain stock zips I have will also return you to stock, but the way it was when you got it new before registering.
3) with the SD card image, do i need to put a specific image on the specified sd card. i.e. 4gb SD gets a 4gb image? or is the image universal to whatever size SD card i get?
3a) What problems am i going to run into using my mac to make the SD card, if any? what program do i need to use?
Click to expand...
Click to collapse
Since you have a Mac, the best way to do it is the new procedure without burning an image. Since I don't have a Mac, I don't know the exact programs to use. I think SDFormatter comes in a Mac version. And I know there are lots of mac partitioning programs to set the first partition active. And using the procedure does use all of the SD, so it is best to use a relatively small one, 2-4GB.
4) when you back up through CWM where does it save it? to the SD card?
4a) this is where i was confused about the image, reading into some of the posts it led me to think the image file took up the entirety of the
SD card.
4b)So in the future i could just boot from the SD card and would have the option to flash the stock rom back on the HD+ if desired? and/or
go back to CM?
Click to expand...
Click to collapse
It saves it either to the SD card or internal memory, you choose.
Yes it uses all of the SD if you use the new procedure. But you need that if you choose to backup to SD. A backup takes about 1.5GB.
And yes, save the SD for future use, like restoring backups or installing new ROMs.
5) what is DUALBOOTING? and NANDROID? how do they tie into CWM and CM10. very confused about this.
Click to expand...
Click to collapse
Dual booting means having one operating system on internal memory (also called emmc for Embedded MultiMedia Card) and one installed to a bootable SD. Most people that dual boot have stock on internal and CM on SD. They are separate and independent from each other.
Nandroid just means internal memory. So a nandroid backup means backing up whatever you have on internal memory.
6) any disadvantage to flashing the EMMC vs booting from SD card every time? I THINK i want to flash the emmc, i don't want to be tied to booting from the SD card everytime- if I'm understanding that correctly.
Click to expand...
Click to collapse
The only advantage to booting to CM on SD is it leaves internal memory untouched for warranty reasons. The disadvantage is it runs slower and is less stable.
7)what is this "trim" lag problem? couldn't really figure out what people were talking about.
Click to expand...
Click to collapse
LAG is a complex issue to explain. If you are used to hard drives getting fragmented and slowing down your system, LAG is similar but a different mechanism with solid state flash drives. TRIM is a process to undo what causes LAG. But some of the solid state chips in these devices have a bug and when TRIM is run, it bricks the chip, making it unusable.
thanks a ton for any help you can give me- I'm sure you receive a lot of questions!
-Sonny
Click to expand...
Click to collapse

leapinlar said:
CWM (ClockworkMod) is a recovery program that allows you to do just what you said. TWRP is also a recovery, but uses the touch screen instead of hardware keys to control it.
You can either use the CWM backup tool to return your device to stock (including any data you have already created, like registration) or the plain stock zips I have will also return you to stock, but the way it was when you got it new before registering.
Since you have a Mac, the best way to do it is the new procedure without burning an image. Since I don't have a Mac, I don't know the exact programs to use. I think SDFormatter comes in a Mac version. And I know there are lots of mac partitioning programs to set the first partition active. And using the procedure does use all of the SD, so it is best to use a relatively small one, 2-4GB.
It saves it either to the SD card or internal memory, you choose.
Yes it uses all of the SD if you use the new procedure. But you need that if you choose to backup to SD. A backup takes about 1.5GB.
And yes, save the SD for future use, like restoring backups or installing new ROMs.
Dual booting means having one operating system on internal memory (also called emmc for Embedded MultiMedia Card) and one installed to a bootable SD. Most people that dual boot have stock on internal and CM on SD. They are separate and independent from each other.
Nandroid just means internal memory. So a nandroid backup means backing up whatever you have on internal memory.
The only advantage to booting to CM on SD is it leaves internal memory untouched for warranty reasons. The disadvantage is it runs slower and is less stable.
LAG is a complex issue to explain. If you are used to hard drives getting fragmented and slowing down your system, LAG is similar but a different mechanism with solid state flash drives. TRIM is a process to undo what causes LAG. But some of the solid state chips in these devices have a bug and when TRIM is run, it bricks the chip, making it unusable.
Click to expand...
Click to collapse
THANK YOU.. so much answered for me

Please help me understand technical details of Safestrap

Hey guys,
I am REALLY impressed with what Hashcode has done (I sent him a donation, totally deserved) but I would like it if someone explained Safestrap to me a bit more in detail. I read the Safestrap thread, but I don't feel like it explained technical details of it. This is just to satisfy my curiosity of what is actually happening.
I will also ask questions about what I don't understand and I hope someone can help me understand more clearly what is happening.
Can someone help me understand the boot process of Android? From what I understand, the bootloader will only boot signed kernels, kinda like some of the new motherboards are doing (or are capable of doing). How does this differ when safestrap is introduced?
How does Safestrap "partition" or break up the different slots? Is it creating new partitions? Is it creating files that are then mounted as partitions?
Do the partitions use the same space for saving application preferences? Or is each environment (slot) separate and isolated from each other?
I'd really like to know more details! Thanks for any help and explanations.

woodsdog said:
Hey guys,
I am REALLY impressed with what Hashcode has done (I sent him a donation, totally deserved) but I would like it if someone explained Safestrap to me a bit more in detail. I read the Safestrap thread, but I don't feel like it explained technical details of it. This is just to satisfy my curiosity of what is actually happening.
I will also ask questions about what I don't understand and I hope someone can help me understand more clearly what is happening.
Can someone help me understand the boot process of Android? From what I understand, the bootloader will only boot signed kernels, kinda like some of the new motherboards are doing (or are capable of doing). How does this differ when safestrap is introduced?
How does Safestrap "partition" or break up the different slots? Is it creating new partitions? Is it creating files that are then mounted as partitions?
Do the partitions use the same space for saving application preferences? Or is each environment (slot) separate and isolated from each other?
I'd really like to know more details! Thanks for any help and explanations.
Click to expand...
Click to collapse
creates virtual ROM-slots, not partitions
http://blog.hash-of-codes.com/how-to-safestrap/ it uses your freed space on your phone

woodsdog said:
Hey guys,
I am REALLY impressed with what Hashcode has done (I sent him a donation, totally deserved) but I would like it if someone explained Safestrap to me a bit more in detail. I read the Safestrap thread, but I don't feel like it explained technical details of it. This is just to satisfy my curiosity of what is actually happening.
I will also ask questions about what I don't understand and I hope someone can help me understand more clearly what is happening.
Can someone help me understand the boot process of Android? From what I understand, the bootloader will only boot signed kernels, kinda like some of the new motherboards are doing (or are capable of doing). How does this differ when safestrap is introduced?
How does Safestrap "partition" or break up the different slots? Is it creating new partitions? Is it creating files that are then mounted as partitions?
Do the partitions use the same space for saving application preferences? Or is each environment (slot) separate and isolated from each other?
I'd really like to know more details! Thanks for any help and explanations.
Click to expand...
Click to collapse
Safestrap does not change your kernel. It is simply the same as multi OS boot on a PC. SS still uses the original kernel but during boot the bootloader is redirected to the ROMS you have stored in your internal RAM to load instead of the original ROM. You get a menu at boot that allows you to selc original or a slot ROM to boot from. SS as well as the ROMS for it does nothing to or with the Kernel. As of right now the kernel on this phone cannot be touched, much less modified.

So using safestrap, I can switch between stock and a modded rom at will?

jonrobertd said:
So using safestrap, I can switch between stock and a modded rom at will?
Click to expand...
Click to collapse
You have to reboot, but yes you can change when you want. Just keep in mind this method consumes a large amount of internal memory. As space will be taken by each ROM in each slot.

What is a virtual rom slot? If it's a pre-determined space, then it's not just a directory on the file system.
I see you can put custom /data on there up to 4GB. What is the default system one without safestrap?
I'd be really curious to almost see this in a diagram of the internal SD card, or understand it well enough to create my own.
Still trying to understand the magic...

woodsdog said:
What is a virtual rom slot? If it's a pre-determined space, then it's not just a directory on the file system.
I see you can put custom /data on there up to 4GB. What is the default system one without safestrap?
I'd be really curious to almost see this in a diagram of the internal SD card, or understand it well enough to create my own.
Still trying to understand the magic...
Click to expand...
Click to collapse
First it is not done on the SD card. it is done on the internal RAm that is 16 or 32 GB depending on your model.
Just imagine aside form the stuff that is already written to your RAM there are now reserved sections that we call slots. Those reserved sections are where the virtual ROM is kept. Just think of the internal RAM as a tower with lets just say 32 floors to keep it simple. Each of those floors are 1 GB tall. Safestrap reserves 4 each of those floors times 4 for it's own use to store ROMS in. So think of a section of that tower consisting of 16GB now belonging to Safestrap for ROM storage and use. The rest is open for the system to use but those 16 floors/slots cannot be touched by the system. I really don't know how to make it simpler and this may be too simple.

Thanks, this is extremely helpful and interesting!