Hey all,
Just ordered (from Amazon) an N1 to use as a dev phone, and had a few questions.
In using later versions of Android, I gather that partitions need to be set up on the SD card. I plan to get a 32 GB class 10, but would like to know what are some good general rules for partitioning with either 4EXT or CWM recoveries.
Also, how do I identify which version N1 I have? I understand some have SLCD and some have AMOLED. Also, some work internationally and some not(?)
Thanks for your input.
Sent from my Dell Streak 7 using Tapatalk 2
All your questions could be solved by searching.
Internal memory can be partitioned using BlackRose. Read the thread so you understand what you're doing, before you actually start partitioning. If you're stuck: search. There have been dozens of threads started by people who didn't read enough.
µSD card can be partitioned with EXT4 recovery, or using partitioning software on your computer (e.g. GParted). Do NOT use ClockworkMod recovery for partitioning.
You can identify your Nexus One screen and network (or FAQ Q13).
Also, the wiki and Wikipedia contain a lot of basic info.
tommert38 said:
All your questions could be solved by searching.
Internal memory can be partitioned using BlackRose. Read the thread so you understand what you're doing, before you actually start partitioning. If you're stuck: search. There have been dozens of threads started by people who didn't read enough.
Click to expand...
Click to collapse
I understand the immediate frustration some of my questions may bring, but believe me, I searched. I spent the entire weekend researching and familiarizing myself with the Dev section, the Q/A section and the General section. These questions were what I was left with - in fact, I read through nearly a year of posts just in the Dev section. I spent time doing general Google searches and more time spent with frustrating xda searches which are generally not very helpful.
FYI, I have rooted & s-offed my DInc, DInc2 and Rezound, and have NVFlashed Honeycomb on my Dell Streak 7, so spending an appropriate amount of time searching is not an issue for me. I hope not to trouble this forum with too many questions in the future.
µSD card can be partitioned with EXT4 recovery, or using partitioning software on your computer (e.g. GParted). Do NOT use ClockworkMod recovery for partitioning.
Click to expand...
Click to collapse
Fair enough - I will use GParted - it's a tool I should have in any case - thank you. That part of my question primarily had to do with the coded partitions table most devs put on their GB/ICS ROM splash pages - XX/XX/XX - what is the naming convention for the sizes given? eg, /system part./recovery part./???
You can identify your Nexus One screen and network (or FAQ Q13).
Also, the wiki and Wikipedia contain a lot of basic info.
Click to expand...
Click to collapse
Having had two other HTC devices, the Wiki is great, but many of the links are broken and many of them do not give basic starter information. In other words, the information is familiar to people who have rooted or are dev'ing for the phone for years, but not to someone new to a Nexus device.
Also, thanks for the link to help ID the version of my device - very much appreciated - I should have looked in the FAQ first.
WookieFan said:
I understand the immediate frustration some of my questions may bring, but believe me, I searched. I spent the entire weekend researching and familiarizing myself with the Dev section, the Q/A section and the General section. These questions were what I was left with - in fact, I read through nearly a year of posts just in the Dev section. I spent time doing general Google searches and more time spent with frustrating xda searches which are generally not very helpful.
FYI, I have rooted & s-offed my DInc, DInc2 and Rezound, and have NVFlashed Honeycomb on my Dell Streak 7, so spending an appropriate amount of time searching is not an issue for me. I hope not to trouble this forum with too many questions in the future.
Fair enough - I will use GParted - it's a tool I should have in any case - thank you. That part of my question primarily had to do with the coded partitions table most devs put on their GB/ICS ROM splash pages - XX/XX/XX - what is the naming convention for the sizes given? eg, /system part./recovery part./???
Having had two other HTC devices, the Wiki is great, but many of the links are broken and many of them do not give basic starter information. In other words, the information is familiar to people who have rooted or are dev'ing for the phone for years, but not to someone new to a Nexus device.
Also, thanks for the link to help ID the version of my device - very much appreciated - I should have looked in the FAQ first.
Click to expand...
Click to collapse
Asking questions is ok, as a matter of fact, that's what this forum is for (partially). It's not (or less) ok if it's a question that has been asked several times before. If you can't find it: learn to search This Nexus One forum is 2,5 years old, it's unlikely you'll experience a unique issue.
I would recommend using 4EXT recovery for partitioning your µSD, as it does that well and you can check partition alignment with it. If you do want to use GParted, make sure your fat32 partition is first and your ext partition last. And make sure the ext partition isn't larger than 1536MB. Larger can cause trouble. And don't use a swap partition.
If you read the BlackRose thread, you will find out that partition layout XX/XX/XX is for internal memory only and represent System/Cache/Data partitions. Stock partition layout is 145/95/196, all in MB.
Enjoy your Nexus One!
tommert38 said:
Asking questions is ok, as a matter of fact, that's what this forum is for (partially). It's not (or less) ok if it's a question that has been asked several times before. If you can't find it: learn to search This Nexus One forum is 2,5 years old, it's unlikely you'll experience a unique issue.
I would recommend using 4EXT recovery for partitioning your µSD, as it does that well and you can check partition alignment with it. If you do want to use GParted, make sure your fat32 partition is first and your ext partition last. And make sure the ext partition isn't larger than 1536MB. Larger can cause trouble. And don't use a swap partition.
If you read the BlackRose thread, you will find out that partition layout XX/XX/XX is for internal memory only and represent System/Cache/Data partitions. Stock partition layout is 145/95/196, all in MB.
Enjoy your Nexus One!
Click to expand...
Click to collapse
Well I am definitely enjoying my N1 - thanks to your help I was able to determine that specific hboots can be flashed to change stock partition layouts.
Even started experimenting with cooking my own ROMs. Really enjoying the "new" phone!
Sent from my Nexus One using Tapatalk 2
Related
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
I have a Dell Streak 7 (T-Mobile version) 3.2 Honeycomb, installed via "[Guide]New HC Rom: 506/507 + Installation Instructions [Including US 4G]". Everything works great, except I have run out of application space.
I have over 11 gigs free, but with 3.2 you can't install anything on the internal SD, or external SD for that matter. I bought 32gig SD cards to store files, I want all the internal storage for Applications and settings.
How can I make the internal storage be one large data partition or at least increase the data partition size, while decreasing the internal SD size.
And for how I ran out, the free apps from Google and Amazon. I have about 200 from the Amazon Free App A Day promotion alone.
aquillasupra said:
I have a Dell Streak 7 (T-Mobile version) 3.2 Honeycomb, installed via "[Guide]New HC Rom: 506/507 + Installation Instructions [Including US 4G]". Everything works great, except I have run out of application space.
I have over 11 gigs free, but with 3.2 you can't install anything on the internal SD, or external SD for that matter. I bought 32gig SD cards to store files, I want all the internal storage for Applications and settings.
How can I make the internal storage be one large data partition or at least increase the data partition size, while decreasing the internal SD size.
And for how I ran out, the free apps from Google and Amazon. I have about 200 from the Amazon Free App A Day promotion alone.
Click to expand...
Click to collapse
My suggestion to you is to flash DJ Steve's HoneyStreak using the NVFlash method. Inside the folder he allows for up to a 6GB app partition if you wanna take it that far... as far as I know of that's the only way to repartition your internal SD.
Create backups of all those apps, create backup of everything on your internal sd because the process is going to wipe everything, and then reinstall and copy back
Any Fixes?
Even I am stuck there. Did anybody find any solution to this.
Can I use the CWM to create a new data partition? I am having rooted Stock 3.2.
rguptan said:
Even I am stuck there. Did anybody find any solution to this.
Can I use the CWM to create a new data partition? I am having rooted Stock 3.2.
Click to expand...
Click to collapse
Did you not read my post, THAT is the easiest solution... I can't think of any way to install 6 gigs of apps, but some people just don't know when to quit installing without realizing what it does to the OS... and even that can be modified if you know how to configure the specific sectors of the internal SD, but I have no experience with that
cdzo72 said:
I can't think of any way to install 6 gigs of apps, but some people just don't know when to quit installing without realizing what it does to the OS...
Click to expand...
Click to collapse
But 6 gb?= I think thats quite enough to use 100+ apps.
exebreez said:
But 6 gb?= I think thats quite enough to use 100+ apps.
Click to expand...
Click to collapse
I'm with you man but I get so frustrated by the noobs that don't realize the reason they were given the option to install to SD in the first place... back in those days when it was necessary and apps were actually coded to run well off an external SD it was ok, but they don't understand that most apps these days prohibit it for many reasons, they just demand too much to run off the external SD and they don't seem to wanna use their brains and wrap their heads around the idea that there's no sense in having hundreds of apps installed... hopefully within the next year those types will either move to the iPhones they should be using because they have no business using a flexible android device or they will frustrated and get talked into buy a brokenglass (windows) phone
I think you should stop using your power to think about those fags.
At this point the question of the OP is answered, isnt it?
If there is another question to this topic please write down. For other questions make a thread.
Btw. whos afraid of asking, is free to PM me, ill answer in max 24h.
exebreez said:
I think you should stop using your power to think about those fags.
At this point the question of the OP is answered, isnt it?
If there is another question to this topic please write down. For other questions make a thread.
Btw. whos afraid of asking, is free to PM me, ill answer in max 24h.
Click to expand...
Click to collapse
Within the thread the question may be answered several times, that won't stop a noob from asking it again, much less keep a moderator from pointing out it has already been asked and solved
cdzo72 said:
Within the thread the question may be answered several times, that won't stop a noob from asking it again, much less keep a moderator from pointing out it has already been asked and solved
Click to expand...
Click to collapse
The noob isnt the you who is guilty so its sinless.
This is what I ended up doing
From the CWM recovery I created a ext3 partition on my SD Card and use Link2SD from market.
Thanks to
http://forum.xda-developers.com/showthread.php?t=1490563&highlight=link2sd
To resize the partition later I had used GParted from a linux live CD.
Honeystreak partition method
I wanted to test a theory on this myself. So I will start with saying I am running 3.2 official with 514(rooted). I use 514 to be able to use my dock. Love me or hate me.
1) I did a nandroid backup on my sd card. I used my app backup tool to backup my apps just in case.
2) I flashed Honeystreak R2 using NVFLASH.
3) I then placed Honeystreak R8 on my sd card with the text file as instructed. and then installed the zip using CWM.
4) I then fastbooted the latest (and greatest) CWM 5.0.2.8
5) Then booted CWM 5.0.2.8 and flashed my Nandroid Backup.
6) CHA-CHING!!!!
I was able to keep the 4 GB partition that was created using the Honeystreak R2 NVFLASH.
This is tested and it works so you can get up to 6GB using this method.
OK i know their are loads of posts about this but i was wondering if any one can start a step by step process from i.e new phone with crap internal memory, to using the sd card (mine is a 2gb one) as internal memory,
so if its possible to go from step one to however many it takes in a simple readable way for any and all noobs (me) i would be sooo great full and screenshots would go along way too.
much appreciated
David
davidbaron89 said:
OK i know their are loads of posts about this but i was wondering if any one can start a step by step process from i.e new phone with crap internal memory, to using the sd card (mine is a 2gb one) as internal memory,
so if its possible to go from step one to however many it takes in a simple readable way for any and all noobs (me) i would be sooo great full and screenshots would go along way too.
much appreciated
David
Click to expand...
Click to collapse
that's lazy!
ive made so many threads doing this and spent ages sorting screenshots and guides out.please use them! in the other post earlier i stated what order you need to follow. please use the correct guides. if you use the guides and get stuck and i don't mean at the first 1 step either...then ill help. the only pointer i will give is this.> http://forum.xda-developers.com/showthread.php?t=1704495 basics/ http://forum.xda-developers.com/showthread.php?t=1565898 ext3
use the search function next time or a mod will step in over me.
After literally days upon days of searching and multiple failed attempts with apps from the Google Play store, I have literally given up hope and burned out here to ask you, my fellow xda members, for some much needed help.
I am trying to mount my 32 GB sdcard to my LG Thrill 4G. I bought the card to replace my previous 16 BG card since I ran out of space. I know from experience with older Android devices that the main filesystem supported is FAT32. Sadly, FAT32 only supports smaller file sizes before it loses it's ability to adequately maintain its stability. I had over 16 GB of data backed up on my windows 8 PC that I transferred to my new 32 GB card (formatted to FAT32 at the time), and I then found out the results the hard way. Luckily I kept the data on my PC, because once I placed the sdcard into my phone it read only 4 GB used. It was as if over 12 GB of data transferred had never existed -_-
I then formatted the sdcard to NTFS. Since it's a much more stable filesystem it has no issues retaining all of my data, but the main problem is still the same: Android won't read NTFS by default.
I read online how some phones with the FUSE module (fuse.ko) built in could effectively read and/or write to NTFS drives with the use of some market apps such as Paragon NTFS or similar, with a rooted device of course. I checked the thread HERE for info on how to get NTFS to read and write successfully on Android, but the main kicker is still whether or not the phone possesses the FUSE module. And, of course, the LG Thrill 4G/Optimus 3D has no built in FUSE driver, which brings me to my main question in all of this:
How do you compile a fuse.ko driver from kernel source to work on an Android phone? More specifically, the LG Thrill 4G.
I've looked in Google Code, github, everywhere....nothing anywhere gives any clue as to how to create the module. There aren't even any kernels available with FUSE/NTFS support.
I'm stumped I've given up trying and failing time and time again. I need the full 32 GB of my sdcard for my data, and it even says in most specs for new smartphones anymore that up to a 32 GB card is supported.....so why hasn't Google made full NTFS or exFAT support for Android yet?
Anyone who can help is GREATLY appreciated. I believe I speak for other individuals including myself when I say a good tutorial on how to this would be worth it's weight in gold at this point. I spent over $30 on this card, and so far I've still not managed to get it to mount and read/write on my phone
Thanks in advance,
-MrDaggs
.....Nothing?
C'mon guys, I know it's probably not the easiest question out here right now, but surely SOMEONE can help me? Or perhaps direct me toward where I would need to go to learn how to do this myself? I've seen other users here on xda asking questions related to compiling the fuse.ko driver and they got an immediate answer, of course they weren'y exactly asking about how to go from step 1, but the point is the same...
ANY help on this will be greatly appreciated. Everyone here on XDA has helped me out a lot in the past, if anyone has anything to say let me know.
Thank you..
Not sure why it jacked up for you
MrDaggs said:
C'mon guys, I know it's probably not the easiest question out here right now, but surely SOMEONE can help me? Or perhaps direct me toward where I would need to go to learn how to do this myself? I've seen other users here on xda asking questions related to compiling the fuse.ko driver and they got an immediate answer, of course they weren'y exactly asking about how to go from step 1, but the point is the same...
ANY help on this will be greatly appreciated. Everyone here on XDA has helped me out a lot in the past, if anyone has anything to say let me know.
Thank you..
Click to expand...
Click to collapse
I have a 32GB card and am using over half of it right now. I'd say you either have a bad card or bad data back-up.
cougargt said:
I have a 32GB card and am using over half of it right now. I'd say you either have a bad card or bad data back-up.
Click to expand...
Click to collapse
I bought A Samsung Class 10 micro SD Card online for about $25....I plugged it into my computer first to transfer the data from my old card I had backed up onto the new card. It would reach about 20-30% finished and then tell me the drive was "corrupted and unreadable". That problem was when I at first left the filesystem unchanged (FAT32). I formatted the sd card to NTFS and tried the process again and it worked flawlessly, only now it won't read in my phone because of the NTFS filesystem :/
I gave my father a 32GB card for his Galaxy SIII a few months ago and his works fine. I don't know what might be wrong with the one I have, though....IF there is something wrong with it.
I'm beyond confused right now..
Bump for answer
stillsober said:
Bump for answer
Click to expand...
Click to collapse
not sure why you need to use ntfs but i think the fone should be able to mount ext2 drives ?
schneidz said:
not sure why you need to use ntfs but i think the fone should be able to mount ext2 drives ?
Click to expand...
Click to collapse
External Hard drive
This post was from years ago, but I noticed I never posted my results. The seller I bought the card from on eBay was a fraud and was removed from the site, I received a refund. The card was corrupted out of the box, and as a result would not mount regardless of the filesystem I tried to implement. Though Android is mainly compatible with FAT32, so my efforts were in vain anyway. Thank you all for your help, this thread is now officially closed.
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!