Related
In short:
Is there a thread somewhere stating the pro's and con's of running Android from different types of "media" (SD, NAND, EXT2)?
If there is, please provide a link, I can't seem to find anything that isn't an unanswered question or small comments.
If there isn't, let this be a starting point for those looking for the answer to this question.
Longer:
I've seen this question pop up once and again but it might be that the topic is totally exhausted and people have stopped commenting on it. I can't seem to find an answer though; What are the pro's and con's of using NAND, EXT2, FAT32 or any combination of it?
I see a couple of installation alternatives and some I have been able to conclude myself but others not.
* Running from SD-card using HaRET
This option is the slowest in terms of Android performance. It has the added value of easily getting back to Windows Mobile by rebooting the phone, gaining easy access to the SD card and manipulation options.
* Running the system AND data on NAND
This option has in my view the fastest Android experience. Access to files on the SD card is a bit more cumbersome (there is the SD card split widget APK available but I have yet to see it working) and access to files for manipulation I can't comment on (haven't gotten to that yet).
* Running the system from NAND and data on EXT2
The performance seems almost as fast as the system+data on NAND. I have no idea about the added value of running anything from an EXT2-partition in the SD card but I'm guessing it will be slower. I have no idea if file access for manipulation is easier or not compared to the other options.
* Running the system AND data from EXT2
I have not tried this yet and cannot comment on it. Something tells me it will be slower than NAND because of SD card overhead.
* Running the system from EXT2 and data on NAND
I have not tried this yet and cannot comment on it.
Now, I've missed out on several of the installation options but I'll edit this post as soon as I get to investigating it further.
Any comments/experience/knowledge in this is greatly appreciated, as it can make things clearer as to what options to choose.
Well these are very good question and wanted to start a thread on this matter as well. I also could not find a strait answer anywhere.
I also want to know if there is an advantage using ext2 over fat32.
So, people out there having knowledge about this matter please share it.
Ext2 and Fat32 are both types of filesystem used on various different types of media, including SD card, Hard drives etc.
EXT2 is (one) of the native linux filesystems, and is fully supported in kernel, and is usually faster and more stable in that OS
FAT32 is the 32bit version of the old MSdos filesystem, used up to Windows 98, and still supported by windows machines, but slower and less stable than the native NTFS filesystem used by XP and above.
Nand is actually the type of flash ROM used by our devices, and not a filesystem as such, and running Android in Nand refers to where the information is stored, rather than the filesystem used to store it.
It's equally valid to say that we run WM in Nand also.
I think that in the case of Android EXT2 should be faster and more stable than fat32 since it's designed for Linux, and works better in that OS.
Zenity ik would like to thank you very much as this answers mij questions.
And i think this would many others aswell.
Don't forget - if you format your MicroSD to just EXT2 then you will make it very awkward to transfer files to/from the card on a Microsoft Windows based system.
This may, or may not be a problem for you.
Ultimately, the current ideal situation (IMHO) is to run your OS from NAND, and to store your data (music / movies / documents) on a FAT32 format MicroSD - as this enables you to swap the MicroSD card without turning off the device, and provides best cross-platform usability of the MicroSD for the purposes of transferring data to/from it.
Thank you all!
Thank you all for commenting! I will add your comments to the Android-wiki I'm building as this question could come back repeatedly from newcomers (and old ones who forgot )!
boli99 said:
Don't forget - if you format your MicroSD to just EXT2 then you will make it very awkward to transfer files to/from the card on a Microsoft Windows based system.
This may, or may not be a problem for you.
Ultimately, the current ideal situation (IMHO) is to run your OS from NAND, and to store your data (music / movies / documents) on a FAT32 format MicroSD - as this enables you to swap the MicroSD card without turning off the device, and provides best cross-platform usability of the MicroSD for the purposes of transferring data to/from it.
Click to expand...
Click to collapse
There is a program for allowing the mounting of EXT2 file systems on windows, however they are not signed. This is more problematic in Windows that are 64bit. The program is called 'ext2fsd' and you can get it from source forge. EXT2 is a better file system, and does not have the 4GB file size limit, and does not fragment (although on a SD card, this should not be an issue). EXT2 also has file permissions that Linux understands. Fat32 has no Access control file permissions.
I have just recently got polymod's eclair running with both system and data on ext2 partitions.
my question is...
I am just wondering what the boot order is...
and where(if possible) can it be changed?
system.img in the andboot folder VS system on partition.
I know it can be set in the installer. but lets say I had installed system on ext2 partition. and then later placed a system.img in the andboot folder.
can I swap between the two?
OK...
I figured it out myself,
You can use the installer to select boot options (Not just options to install)
so I have a system and data on partitons. (currently using)
and I also have a second build installed to .img files in the andboot folder. (for failsafe backup)
if I want to swap from one into the other
I enter installer and change the settings for the system and data to
their respective locations and then just QUIT.
I also still have a donut build in the android folder. as well as still running winmo.
quad boot system on my phone...LOL
Now thats a neat use of the installer, I think this find deserves it's own thread in fact, I'm certain others will find it useful
Tanks !
binlabin said:
* Running the system from NAND and data on EXT2
The performance seems almost as fast as the system+data on NAND. I have no idea about the added value of running anything from an EXT2-partition in the SD card but I'm guessing it will be slower. I have no idea if file access for manipulation is easier or not compared to the other options.
Click to expand...
Click to collapse
I've done some tries with this doing the partitioning from within android and then formatting the FAT32 partition from Windows 7 but the FAT32 partition doesn't work very well afterward. Really slow and sometimes crashes the explorer. Propably something to do with my SD-card. May try doing the partitioning and formatting from Linux to see if it works better.
Seems to me the main advantage of this option is to increase the size of available data storage which i suspect can become a limitation sooner or later in a pure NAND install.
EDIT: Now I've done it and gone NAND-System + EXT2-Data... Partitioned the SD-card from Ubuntu with gparted. Resized the FAT32 partition and created 3 primary EXT2 partitions. only the second (partition 3) should be used though with the setup I am using. It's charging right now so I haven't tried it out much yet but I will later on. However I noticed that I now have 171Mb free phone storage instead of 30-something that I had before (same apps installed).
EDIT2: Ran gparted again and shrinked the unused partition (partition 2) and expanded the data partition (partition 3) so I now have 369Mb free "Internal phone storage". Haven't noticed any speed differences between this and when I had data on NAND.
nand
By then one question:
If im install android in the NAND is more fast ready? But this process erase WM6?
Because now android work good in my HTC TYNT II but the camera and bluetooth not work and have one or two performance problems and for this dont like delete WM6 of my phone, and for this im use Android from my SD.
But look the NAND option because have a problems with the time live of my battery only lasts 5hours with android and SD.
Thanks for your help and cooperation
excellent thread which answers some questions that I had. Thanks to everyone who contributed. The only question remaining though and I have posted this elsewhere without getting an answer:
I partitioned a 2 gb sdcard with ~1.6gb Fat32 and the rest as a single Ext2. I selected system on nand and data on ext2 in the installer. After installation, it does show alot more memory for data as compared to data on nand, BUT I also have a data.img in andboot which is in the Fat32 partition, with a size around 250mb. The question is, is the data in that file or on ext2? If I backup data from installer, it creates a databackup.img in andboot with the same size as data.img. Seems to me the ext2 partition is just taking up space and not being used. Can anyone more knowledgeable shed some light on this? Thanks.
Not quite sure what is going on there, seems very counter-intuitive, I would have assumed that system on Nand, data on EXT2 would have installed the data partition to EXT2 on SD. This would seem not to be the case in this instance.
There are a few experiments you could try, if you are brave enough, since you may cause problems by trying any of these suggestions, which could mean a reinstall, I leave it to your judgement how to proceed
Ok firstly I assume you have a card reader, since you managed to partition and format the SD card in the first place. Remove the SD card, insert in card reader, delete the andboot folder, or the contents of the folder, ( may be wise to have a spare SD with either a winmo or android install handy at this point, just in case things go horribly wrong ).
Now with the cleaned SD, put it in the phone and boot, it should boot fine, IF the data is truly on the EXT2 partition.
That at least will answer one question, namely, where the heck is my data?
If this works fine, then I'd just put it down to some inner weirdness of android on non-native devices, if it fails then I'm wondering if your EXT2 partition may have problems, forcing the phone to dump it on the first available good partition, namely the FAT32 one.
Oh and if it does fail, you will have to reinstall, since your data will be toast.
Finally, good luck, I await with interest
As I recall, the install has the FAT32/Ext2 options incorrectly swapped. It has been this way for a while.
zenity said:
Not quite sure what is going on there, seems very counter-intuitive, I would have assumed that system on Nand, data on EXT2 would have installed the data partition to EXT2 on SD. This would seem not to be the case in this instance.
There are a few experiments you could try, if you are brave enough, since you may cause problems by trying any of these suggestions, which could mean a reinstall, I leave it to your judgement how to proceed
Ok firstly I assume you have a card reader, since you managed to partition and format the SD card in the first place. Remove the SD card, insert in card reader, delete the andboot folder, or the contents of the folder, ( may be wise to have a spare SD with either a winmo or android install handy at this point, just in case things go horribly wrong ).
Now with the cleaned SD, put it in the phone and boot, it should boot fine, IF the data is truly on the EXT2 partition.
That at least will answer one question, namely, where the heck is my data?
If this works fine, then I'd just put it down to some inner weirdness of android on non-native devices, if it fails then I'm wondering if your EXT2 partition may have problems, forcing the phone to dump it on the first available good partition, namely the FAT32 one.
Oh and if it does fail, you will have to reinstall, since your data will be toast.
Finally, good luck, I await with interest
Click to expand...
Click to collapse
Great idea, I'll try this on the weekend. I wont delete data though, I'll just rename andboot and backup data for good measure, because I want to be able to go back to the data by renaming it back if it doesn't work. I was also thinking if there is any way to get to the ext2 partition and read it... I'm on xp so I cant do it on my pc, and on the phone, I've looked around in astro n other file managers but cant see anything. But if the case is as golfnz34me points out, then I should just backup the data, and change the option to Fat32 in install and restore data. That should do the trick.
golfnz34me said:
As I recall, the install has the FAT32/Ext2 options incorrectly swapped. It has been this way for a while.
Click to expand...
Click to collapse
Thanks, will check this out. If its true, then great, more speed for my /data! I wonder how I missed this, been going through these forums regularly...
Ok I checked it out, and golfnz34me is correct it seems.
But now I found a new problem. I backed up data, and in the installer, set the data to SDCard, and tried to restore data. It gives various errors like
Code:
cannot determine filesystem size
failed
failed to format
...some other lines...
losetup: /dev/block/loop2: no such device or address
I created the partition with Paragon partition manager, and after getting this error I rechecked in PPM. I reformated the partition, but still get the error. In PPM the partition drive letter isnt assigned. Or, the partition isnt the active partition. Can one of those be the problem? The volume name is Ext2. Im not very experienced in partitioning etc, apart from normal ntfs partition for new hds in windows, so I didnt play with any options. I dont have a linux system either. Any got any ideas? Any help would be appreciated alot!
Not sure about using partition managers other than gparted, afaik most people are using the Gparted live cd if they don't have a linux install handy.
The errors all point to some sort of problem with the EXT2 partition, or it's formatting.
Also EXT2 partitions do not have drive letters, nor do they have to be active partitions.
Apps and data on SD card.
I cant seem to figure out how to make all the apps and other stuff install to the SD card. Do I have to partition the card into two partitions? or is there a way to install the system to Nand and make all the apps and data go to the SD card? Ive tried setting it to System on nand and data on SD partition but it says no partitions to install to or something.
Message edited by myself :
I have/had a lot of questions about using Android on my Kaiser, so I'm editing this message, integrating my questions and their answers..
1° How to install softwares on the microSD card? (Thanks to l1q1d !)
-> You need a microSD class 4 or more to do it.. Partition like this (for a 2Gb microSD) : 1600 Mb FAT32 + 32 Mb EXT2 + 300 Mb EXT2 with QParted or "Minitool Partition Wizard"
-> During Android's installation, you have to choose System on NAND, and Data on "SD Card Partition" !
2° The camera doesnt works.. Do I need to change the kernel (.nbh file I guess?) or is it a ROM problem? (Thanks to Krazy-Killa!)
-> It is a RADIO problem
-> All radios 1.65.xx make the camera unusable, but phone is stable. All 1.71.xx radios allow camera function but break phone stability.
3° How could I be able to transfer files from my PC to my Android phone? (thanks to myself)
-> Using DoubleTwist (on PC) and DoubleTwist AirSync on your phone! It is like an iTunes, but for Android.
4° How can I access the Android Market and its content from my computer? (thanks to myself)
-> Using DoubleTwist on your computer!
5° How can I watch Youtube videos on my phone? Or, how to watch embedded youtube videos in my browser?
-> Don't know..
6° How can I watch divx videos on my phone?
-> Don't know..
6°
Thanks to everyone!
1° I can't install softwares on the microSD card.. Tried to make a EXT2 partition (1500 Mb FAT32 + 500 Mb Ext2), but it won't use it!
-> If I select "Data on EXT2 Data.img" during installation, it makes a "data.img" file on my FAT32 partition, but I think it is even not using it..
This may sound wierd, but your /data dir is inside data.img. The file is mounted via loop to that dir. Windows analogy, TrueCrypt, although for other purposes.
-> If i select "Data on SDCard partition", it says he's not able to "umount /data"..
Your SD card MUST correctly be partitioned. Windows will not partitions removable drives, please use dedicated software. Take this syntax and apply for you SD size:
For a 4GB sd, 3.2 gb for first PRIMARY partition FAT32, 64mgs for 2nd PRIMARY partition EXT2, 512 mgs for 3rd PRIMARY partition EXT. Your SDcard will be the Fat32 partition, your data the last partition. Adjust acordingly.
2° The camera doesnt works.. Do I need to change the kernel (.nbh file I guess?) or is it a ROM problem?
NBH might be considered a ROM, the kernel (and others) part of it. The Androidinstall.tar might also be considered a ROM, the system part of it (in this case, Android OS).
But yes... perhaps a very wrong mismatch of kernel VS androidinstall.tar
3° I wonder if I could be able to transfer files from my PC to my phone.. If it does, how could I do it?
Not easy. You cannot mount the sd card via USB. Not yet at least.
You will never be able to mount the sdcard if you use the data.img option. (both Android and your computer cannot access at the same time to the sdcard. Cut android from /data, and expect SERIOUS malfunctions.
(i digress... but if /data was in data.img, and /sdcard as in sdcard.img you could mount the sdcard. But then again... Kaiser MMC/SD reader is quite.... SLOW.)
daedric said:
1° I can't install softwares on the microSD card.. Tried to make a EXT2 partition (1500 Mb FAT32 + 500 Mb Ext2), but it won't use it!
-> If I select "Data on EXT2 Data.img" during installation, it makes a "data.img" file on my FAT32 partition, but I think it is even not using it..
This may sound wierd, but your /data dir is inside data.img. The file is mounted via loop to that dir. Windows analogy, TrueCrypt, although for other purposes.
-> If i select "Data on SDCard partition", it says he's not able to "umount /data"..
Your SD card MUST correctly be partitioned. Windows will not partitions removable drives, please use dedicated software. Take this syntax and apply for you SD size:
For a 4GB sd, 3.2 gb for first PRIMARY partition FAT32, 64mgs for 2nd PRIMARY partition EXT2, 512 mgs for 3rd PRIMARY partition EXT. Your SDcard will be the Fat32 partition, your data the last partition. Adjust acordingly.
2° The camera doesnt works.. Do I need to change the kernel (.nbh file I guess?) or is it a ROM problem?
NBH might be considered a ROM, the kernel (and others) part of it. The Androidinstall.tar might also be considered a ROM, the system part of it (in this case, Android OS).
But yes... perhaps a very wrong mismatch of kernel VS androidinstall.tar
3° I wonder if I could be able to transfer files from my PC to my phone.. If it does, how could I do it?
Not easy. You cannot mount the sd card via USB. Not yet at least.
You will never be able to mount the sdcard if you use the data.img option. (both Android and your computer cannot access at the same time to the sdcard. Cut android from /data, and expect SERIOUS malfunctions.
(i digress... but if /data was in data.img, and /sdcard as in sdcard.img you could mount the sdcard. But then again... Kaiser MMC/SD reader is quite.... SLOW.)
Click to expand...
Click to collapse
Thanks for this fast answer.
Do you have any solution to see the camera working?
I partitioned with PartitionWizard for Windows, very useful tool, which is able to support Ext2, etc..
But the problem is that if I select the "SD partition" option (to stock the data) in the Android installer, it says "unable to umount /data"..
I will give it a try with 3 partitions as you said
Edit : okay, so, I made these 3 partitions (on a 2Gb SD) : 1500 Mb FAT32 + 32Mb EXT2 + 300Mb EXT2, it is approximately the same.
Then I boot the phone, I select "Sys on NAND", "Data on SDCard partition", I try to install, some (normal) text appears, but nothing more..
And, if I select "Data on EXT2 Data.img", it makes a "Data.img" in my 1.5Gb FAT32 partition! It makes no sense..
I also have another question : could you explain me the difference between ODEX and DEODEX ?
I made searchs on the web, but not very useful help..
No comment about your search skills....
http://forum.xda-developers.com/showthread.php?t=756659
Oh thanks. This page was even in my bookmarks..
Maybe I saw it but did not read the good lines..
L1qU1d, do you have some answers for my previous questions??
Which one? daedric responded well to all the questions
Not really.
I'm still unable to use the camera (with Froyo ROMs).
And I'm still unable to stock data on a EXT2 partition (in my SDCard)..
Also, I noticed today that I can't install some ROMs, as "Fat Free Froyo"..
With the same options than other ROMs, it wont boot.. So sad!
zebra363 said:
Not really.
I'm still unable to use the camera (with Froyo ROMs).
And I'm still unable to stock data on a EXT2 partition (in my SDCard)..
Also, I noticed today that I can't install some ROMs, as "Fat Free Froyo"..
With the same options than other ROMs, it wont boot.. So sad!
Click to expand...
Click to collapse
Do you mean your front camera or the main camera on the back side of the phone?
Front camera doesn't work in any builds.
Back camera needs to be fixed by flashing another radio.
Radios can be found here:
http://forum.xda-developers.com/showthread.php?t=393182
Funny thing with my case. My camera doesn't work either (but chose not to bother with it), as I have two issues.
1. All radios 1.65.xx make my camera unusable, but phone is stable.
2. 1.71.xx radios allow camera function but break phone stability.
So in my case it's Catch 22, lol. Do I want the camera but an unstable phone or no camera and stable phone.
Sent from my AT&T Tilt using XDA App
Hmm, tried every radio?
If that's the case I would prefer stability above the camera.
Since the camera quality isn't super anyways so.
My Tilt had the 1.65.21.18 radio loaded stock when I got it, still using it to this day and having no trouble with instability, and yes tried all 1.65.xx radios and none allow camera usability. Used all 1.71.x radios, all unstable but camera works, and even then I get one shot out of it and the phone crashes.
Sent from my AT&T Tilt using XDA App
If yo ucahnge te data location in nbheditor - fstab did you get a error?
syntax1993 said:
Do you mean your front camera or the main camera on the back side of the phone?
Front camera doesn't work in any builds.
Back camera needs to be fixed by flashing another radio.
Radios can be found here:
http://forum.xda-developers.com/showthread.php?t=393182
Click to expand...
Click to collapse
I mean both! On the android wiki, they says both are supported..
Krazy-Killa said:
My Tilt had the 1.65.21.18 radio loaded stock when I got it, still using it to this day and having no trouble with instability, and yes tried all 1.65.xx radios and none allow camera usability. Used all 1.71.x radios, all unstable but camera works, and even then I get one shot out of it and the phone crashes.
Sent from my AT&T Tilt using XDA App
Click to expand...
Click to collapse
I'm using 1.70.19.09, and it is even not so stable, and there's no camera.. So sad.. So, do you advise me to install 1.65.x radio?
l1q1d said:
If yo ucahnge te data location in nbheditor - fstab did you get a error?
Click to expand...
Click to collapse
My SD is partitioned like this : 1.5Gb FAT32 + 32Mb EXT2 + 300Mb EXT2
Following your advice, I started ATools and made these changes :
- System -> Auto
- Data -> SD Partition 3 (300 Mb)
- Swap -> SD Partition 2 (32 Mb)
I installed, and at first boot, it says "System is not responding". But after a while (30 secs), it boots, but totally unstable, many problems..
Maybe should I remove the "Swap" option?
Also, another question : how could I know my "LCD Panel" type? I have sometimes display issues like the white screen so I guess "Auto" option is not a good choice.
zebra363 said:
I mean both! On the android wiki, they says both are supported..
I'm using 1.70.19.09, and it is even not so stable, and there's no camera.. So sad.. So, do you advise me to install 1.65.x radio?
My SD is partitioned like this : 1.5Gb FAT32 + 32Mb EXT2 + 300Mb EXT2
Following your advice, I started ATools and made these changes :
- System -> Auto
- Data -> SD Partition 3 (300 Mb)
- Swap -> SD Partition 2 (32 Mb)
I installed, and at first boot, it says "System is not responding". But after a while (30 secs), it boots, but totally unstable, many problems..
Maybe should I remove the "Swap" option?
Also, another question : how could I know my "LCD Panel" type? I have sometimes display issues like the white screen so I guess "Auto" option is not a good choice.
Click to expand...
Click to collapse
Yah the front camera is supported but only in the kernel. Our android builds still don't have the software to utilize the front camera.
If you really want to use the camera try flashing a 1.71.xx radio but if you want stability go 1.65.xx radios.
Swap should actually improve performance, but that also depends on your SD Card Class (class 6 is recomended)
There's really no way to know what lcd panel you have except by experimenting. I'm using Panel 3 though I still get the white screen I don't have any issues with it powering back on. Panel 2 is most common however.
Btw some builds have their launcher on /data. You can check by using the mixer in aTools and possibly move the launcher into /system (Though MAKE SURE you don't overfill /system. No more than 100MB for the /system folder is what I recommend)
If the Launcher is on /data that could explain your slow performance.
Sent from my AT&T Tilt using XDA App
Krazy-Killa said:
Yah the front camera is supported but only in the kernel. Our android builds still don't have the software to utilize the front camera.
If you really want to use the camera try flashing a 1.71.xx radio but if you want stability go 1.65.xx radios.
Swap should actually improve performance, but that also depends on your SD Card Class (class 6 is recomended)
There's really no way to know what lcd panel you have except by experimenting. I'm using Panel 3 though I still get the white screen I don't have any issues with it powering back on. Panel 2 is most common however.
Btw some builds have their launcher on /data. You can check by using the mixer in aTools and possibly move the launcher into /system (Though MAKE SURE you don't overfill /system. No more than 100MB for the /system folder is what I recommend)
If the Launcher is on /data that could explain your slow performance.
Sent from my AT&T Tilt using XDA App
Click to expand...
Click to collapse
I think I will go for stability, I'm using another phone to take pictures, so I dont care about that.
Tried without changing the Swap, but it's still the same, system still crashes..
I can't find this option in aTools mixer.. Or, I don't know how to check it..
My priority is having a good and stable (then maybe fast, also) ROM, with applications installed on my SD card..
Run a search for aTools here on the forums, there should be a thread along with a link to a tutorial on how to use the mixer.
I would but I'm on my phone, and 3G here is crap, lol.
Sent from my AT&T Tilt using XDA App
Krazy-Killa said:
Run a search for aTools here on the forums, there should be a thread along with a link to a tutorial on how to use the mixer.
I would but I'm on my phone, and 3G here is crap, lol.
Sent from my AT&T Tilt using XDA App
Click to expand...
Click to collapse
No problem, thanks for your help.
Which ROM could you advise me, for stability?
NotSoSuperFroyo seems to be very stable, but I can't really judge it..
I installed Radio 1.65.21.18 as yours, and will give it a try!
Also, is there an application to read .AVI (Divx) videos?? As TCPMP (Windows Mobile) or VLC (iPhone / Windows)
Gingerbones, but then again I use it because it's stripped down do much that I can customize it to my liking and let's me isolate problems.
The other is not so super froyo, as it's pretty stable too.
Sent from my AT&T Tilt using XDA App
I think I will edit this topic as a basic FAQ
Could someone teach me how to :
1. Watch youtube videos on Android ?
2. Watch my .avi files ??
3. Take notes (as Windows Mobile notepad, where you can draw & write!) ?
Thanks a lot!
So i have used different ROMs and love android on my kaiser.
However, after a few days use the phone tends to crash and afterwards loses all data(SMS etc) and/or apps. The 2.6.32 kernel seems to be better but this still happens.
So is there a way for this to not happen? I'm currently just restoring data to avoid reinstallign apps and using backup apps to restore SMS etc.
Is this to do with data being on NAND? and if so is there no data loss on SD card but is it slower and can you not remove SD card if you do it that way?
i'm searching that too but i have a big problem with all android roms..
my problem : i can turn on the wi-fi and it shows me the wifi networks... BUT after i pressed on my network and entered my password correctly it says disconnected...
what can i do ? please help me it makes me angry
anyone? i'm sure someone knows what's going on!
Aiex Rlder said:
So i have used different ROMs and love android on my kaiser.
However, after a few days use the phone tends to crash and afterwards loses all data(SMS etc) and/or apps. The 2.6.32 kernel seems to be better but this still happens.
So is there a way for this to not happen? I'm currently just restoring data to avoid reinstallign apps and using backup apps to restore SMS etc.
Is this to do with data being on NAND? and if so is there no data loss on SD card but is it slower and can you not remove SD card if you do it that way?
Click to expand...
Click to collapse
From my understanding the older kernel 2.6.25 is more stable, although it lacks some of the updates that later versions provide.
Installing system to NAND and data to storage card is no doubt the most nonvolatile option at this point. It can run a bit slower, but this can be circumvented by overclocking the CPU using RogueTools (a bit taxing on the battery, however).
It's always a good idea to keep consistent backups made to insure your data is safe. You can never go wrong there. Just be sure you have the latest patch of the current version you've flashed, do a clean system install, add your usual apps, reboot to the boot menu and backup data, then restore data from the same menu. This has been the recommended process mentioned in other threads.
this also happens to me, for a few days everything runs fine, however once in a while (about 2 days) system crashs and i have to restore data (with every apps installed). The problem is that all sms, call log, and some apps settings are wiped.. =( that's not cool ;P
another problem is everytime i reboot, or restore data, 3g is enabled... even if i put on settings "no data". is pain in the ass when my data plan limited exceeds, every time i reboot, carrier charges me more money... any solution? thanks in advance...
You can disable data on boot in the kernel, either in Atools or change ppp.nostart=0 to ppp.nostart=1 with a hex editor. I think the only way to enable data then is with Modem.apk, but most builds have it and if not, you can just copy it from a similar build.
I used it like this for quite a while when I was on a contract with no data plan.
cerebralgenius said:
From my understanding the older kernel 2.6.25 is more stable, although it lacks some of the updates that later versions provide.
Installing system to NAND and data to storage card is no doubt the most nonvolatile option at this point. It can run a bit slower, but this can be circumvented by overclocking the CPU using RogueTools (a bit taxing on the battery, however).
It's always a good idea to keep consistent backups made to insure your data is safe. You can never go wrong there. Just be sure you have the latest patch of the current version you've flashed, do a clean system install, add your usual apps, reboot to the boot menu and backup data, then restore data from the same menu. This has been the recommended process mentioned in other threads.
Click to expand...
Click to collapse
could you possibly point me in the direction of guide for how to put data on storage card? i'm currently using it on NAND and it dies after a few days.
thank you!
Aiex Rlder said:
could you possibly point me in the direction of guide for how to put data on storage card? i'm currently using it on NAND and it dies after a few days.
thank you!
Click to expand...
Click to collapse
you have to split your SD into three primary partitions: FAT32, EXT2 and one more EXT2. Use something like Partition magic or free EASEUS Partition Master to do that.
REMEMBER: all partitions should be Primary, not Logical. FAT32 must go first, or your Windows PC won't detect it.
first is acessible from Windows and is used for storing music, pictures and other stuff. You also place andboot folder to that partition.
second and third are for /data and /swap respectively. /data will contain all your apps, so don't be greedy with its capacity, and /swap is a location for temporary data, so 256 Megabytes are enough.
AFTER YOUR SD IS SPLIT, use atools to assign data and swap to appropriate partitions (SD partition 2 and 3), then flash your Kaiser with such an NBH.
FINALLY, boot up from sd card with Android build in andboot folder, hold the D-pad center for installation menu and select "data to SD partition" option.
Let the installation complete and press Quit to boot into your crashproof Droid.
For me, the MOST MOST MOST stable build were Warbyte's Donut and Myn's Warm Donuts.
Froyo crashes pretty random at bootups due to init.rc corruption. If you want to be handy with android OS and don't messa round alot, I suggest you go with Donut. Froyo does offer you performance but in my opinion its less stable than a usual Donut build with 2.6.25
StripezZ said:
you have to split your SD into three primary partitions: FAT32, EXT2 and one more EXT2. Use something like Partition magic or free EASEUS Partition Master to do that.
REMEMBER: all partitions should be Primary, not Logical. FAT32 must go first, or your Windows PC won't detect it.
first is acessible from Windows and is used for storing music, pictures and other stuff. You also place andboot folder to that partition.
second and third are for /data and /swap respectively. /data will contain all your apps, so don't be greedy with its capacity, and /swap is a location for temporary data, so 256 Megabytes are enough.
AFTER YOUR SD IS SPLIT, use atools to assign data and swap to appropriate partitions (SD partition 2 and 3), then flash your Kaiser with such an NBH.
FINALLY, boot up from sd card with Android build in andboot folder, hold the D-pad center for installation menu and select "data to SD partition" option.
Let the installation complete and press Quit to boot into your crashproof Droid.
Click to expand...
Click to collapse
so youre saying if i do like You said I can reboot as many times as i want and nothong would wipe? and btw. if i use atools to mod boot settings my kaiser freezes when running quadrant benchmark or raging thunder.
dark_prince said:
For me, the MOST MOST MOST stable build were Warbyte's Donut and Myn's Warm Donuts.
Froyo crashes pretty random at bootups due to init.rc corruption. If you want to be handy with android OS and don't messa round alot, I suggest you go with Donut. Froyo does offer you performance but in my opinion its less stable than a usual Donut build with 2.6.25
Click to expand...
Click to collapse
That's right but on Donut lot of aplication dont work.. Lot of aplication woks with Android 2.1+
X46X said:
That's right but on Donut lot of aplication dont work.. Lot of aplication woks with Android 2.1+
Click to expand...
Click to collapse
Say one application which you want for Donut? and it doesn't work on it?
Majority of Developers start building for Donut first since its still primary OS for alot of devices. So far all of the apps worked on Donut for me. ADW, Handful of Widgets, Documents2Go, FruitNinja, and blablabla apps.
Flashplayer doesn't work even on foryo as of yet
StripezZ said:
you have to split your SD into three primary partitions: FAT32, EXT2 and one more EXT2. Use something like Partition magic or free EASEUS Partition Master to do that.
REMEMBER: all partitions should be Primary, not Logical. FAT32 must go first, or your Windows PC won't detect it.
first is acessible from Windows and is used for storing music, pictures and other stuff. You also place andboot folder to that partition.
second and third are for /data and /swap respectively. /data will contain all your apps, so don't be greedy with its capacity, and /swap is a location for temporary data, so 256 Megabytes are enough.
AFTER YOUR SD IS SPLIT, use atools to assign data and swap to appropriate partitions (SD partition 2 and 3), then flash your Kaiser with such an NBH.
FINALLY, boot up from sd card with Android build in andboot folder, hold the D-pad center for installation menu and select "data to SD partition" option.
Let the installation complete and press Quit to boot into your crashproof Droid.
Click to expand...
Click to collapse
Just a correction, to my understanding, 2nd Partition is there for Sys on SD Card Partition, and 3rd Partition is there for Data on SD Card Partition option. If you make a 4th partition with linux swap FS, it will be auto-mounted at startup
dark_prince said:
Say one application which you want for Donut? and it doesn't work on it?
Majority of Developers start building for Donut first since its still primary OS for alot of devices. So far all of the apps worked on Donut for me. ADW, Handful of Widgets, Documents2Go, FruitNinja, and blablabla apps.
Flashplayer doesn't work even on foryo as of yet
Click to expand...
Click to collapse
Zeam Launcher, newest Gmail, Twitter, SoundHound 2.5.2..
X46X said:
Zeam Launcher, newest Gmail, Twitter, SoundHound 2.5.2..
Click to expand...
Click to collapse
Never liked Zeam Launcher, it's just a dumbed down version of ADW in my opinion. But I will agree with the newest Gmail. Hell it's not even supported in Eclair. >_<
Donut is by far the best as it's designed for phones the same age as our Kaiser's, and Eclair would be considered an upgrade option for our phones as well. Froyo on the other hand as well as Gingerbread would be "unofficial" upgrades as they would be too resource hungry for our small devices.
Zeam is pretty snappy but Helix launcher is okay on donut otherwise. Twitter, oh well, there are dozen of apps that tweet for you on your donut. Gmail, I agree. and soundhound, never used it >.<
Eclair isnt as snappy as froyo or donut but worths if software support it. I say that try thoughtlesskyle's Not So Super Froyo or mine build as well. Considering init.rc, its more obvious in updated versions of fresh froyos (usually happens if you reboot with some resource taking process running)
i cannot install a donut release. but the froyo works installing.
I don't know why. any suggestions?
hey,
so i'm using data in a partition on my microsd card and so far is pretty crash proof. unfortunately it's only a class2 one, and so it can be slow and some apps like alarm doesn't work properly, i suspect this is due to the slow microsd card.
Is there a difference in speed between using a partition and using data.img without a partition?
Will using a class 4/6 one solve this problem? getting very close to a stable phone that does all i want!
Apologies if this has been resolved before, but I've been seeing two download folders in my SD card "downloads" and "Downloads." I've tried deleting one but I get an error - this also confuses Recovery when I try to flash a file located in one of the directories it typically looks in the wrong one. Has anyone had this or resolved it?
pongalong said:
Apologies if this has been resolved before, but I've been seeing two download folders in my SD card "downloads" and "Downloads." I've tried deleting one but I get an error - this also confuses Recovery when I try to flash a file located in one of the directories it typically looks in the wrong one. Has anyone had this or resolved it?
Click to expand...
Click to collapse
I have the issue and have just learned to deal with it. I don't really know when it why it happened, sometime around when I first flashed jellybean I think. Idk. Just letting you know you're not alone. Btw the "download" folder appears first in recovery. I move all my roms and kernels there. The "Download" is the folder all the general downloads end up in for me... at least I think... it's confusing but a sms issue to me.
DARKSIDE
I made a folder called Aaroms. It goes alphabetical and capital letters first so that folder is always on the top of the list. I then sort my roms mods and kernels with sub folders.
If you keep your (D)download folder clean and sorted it should be easy to know which one has what
Sent from my Galaxy Nexus using xda premium
This is just speculation, but...
1. I think the virtual sdcard (sdcard0) and its links exists to make the real "sdcard" (/data/media) look like fat to apps instead of ext, which it really is (because it doesn't have a separate partition to itself). Most apps only know how to write to fat on the sdcard.
2. To programs that expect to be writing to fat, "download" and "Download" are the same directory, so they can be careless how they spell it when they access it or create it. But since the real filesystem is ext, they get created as two different directories. Maybe through some case-checking bug in the virtual sdcard or some program that writes directly to /data/media.
3. What I wound up doing was taking all my data out of both directories, deleting one, and making sure the remaining one was named "directory". Then I put all my data back in that one and everything has been good since then.
Well this is Linux after all. Downloads != downloads
Sent from my Galaxy Nexus using xda premium
Need help too
pongalong said:
Apologies if this has been resolved before, but I've been seeing two download folders in my SD card "downloads" and "Downloads." I've tried deleting one but I get an error - this also confuses Recovery when I try to flash a file located in one of the directories it typically looks in the wrong one. Has anyone had this or resolved it?
Click to expand...
Click to collapse
I have the same issue. I have two Download folders. The thing is that the one with the small "D" (download), it is empty, and when I try to delete it, it always reappear.
Help!
this was anwsered like 2 days ago.
sent from my i9250
bk201doesntexist said:
this was anwsered like 2 days ago.
sent from my i9250
Click to expand...
Click to collapse
I cant find the post telling the answer. Lol. The last post isbin october 2010.
strumcat said:
1. I think the virtual sdcard (sdcard0) and its links exists to make the real "sdcard" (/data/media) look like fat to apps instead of ext, which it really is (because it doesn't have a separate partition to itself). Most apps only know how to write to fat on the sdcard.
Click to expand...
Click to collapse
I think that the symlinks are there just for backwards compability issues with apps, that look under /sdcard/ mount point. it doesn't have anything to do with fs, android never used fat, or ntfs; known fs in android are yaffs2, ext4 and maybe a few proprietary ones like sammy's rfs.
bk201doesntexist said:
I think that the symlinks are there just for backwards compability issues with apps, that look under /sdcard/ mount point. it doesn't have anything to do with fs, android never used fat, or ntfs; known fs in android are yaffs2, ext4 and maybe a few proprietary ones like sammy's rfs.
Click to expand...
Click to collapse
The real sdcards were formatted as fat, and most apps that used them to store data only knew how to read/write a fat fs. I found this out by creating a mountable volume on a real sdcard on my old phone. It mounted as a directory on the sdcard. If I formatted the volume as fat, all my apps could use it normally. If I formatted it as ext(anything), a few apps could use it but most could not.
The symlinks are for backwards compatibility, but I believe the fuse filesystem virtual sdcard0 exists to make ext4 look like fat to all apps and to windows.
Note that if the gnex "sdcard" had its own partition, it could be formatted as fat and mounted as USB external storage like a real sdcard. I don't know, but it seems like Google went out of their way to prevent that.
The Google line is that the gnex sdcard shares an ext4 partition to maximize space, ie no unused wasted space on two partitions. But that is pretty farfetched, since the number of problems caused by this arrangement is huge in proportion to the "space saved" which is negligible.
Obviously, the real reason for this kludged-up mess is to discourage local storage/backup and encourage cloud storage, which can then be monetized.
strumcat said:
The real sdcards were formatted as fat, and most apps that wrote data to it only knew how to write it to a fat fs. I found this out by creating a mountable volume on a real sdcard on my old phone. It mounted as a directory on the sdcard. If I formatted the volume as fat, all my apps could use it normally. If I formatted it as ext(anything), a few apps could use it but most could not.
The symlinks are the for backwards compatibility, but I believe the fuse filesystem virtual sdcard0 exists to make ext4 look like fat to all apps and to windows.
Note that if the gnex "sdcard" had its own partition, it could be formatted as fat and mounted as USB external storage like a real sdcard. I don't know, but it seems like Google went out of their way to prevent that.
The Google line is that sdcard shares ext4 partition to maximize space, is no unused wasted space on two partitions. But that is pretty farfetched, since the number of problems caused by this arrangement is huge in proportion to the "space saved" which is negligible.
Obviously, the real reason for this kludged-up mess is to discourage local storage/backup and encourage cloud storage, which can then be monetized.
Click to expand...
Click to collapse
sure, i was talking about nand storage. still, if apps really depend on that to survive (said "fat compability"), it's unlogical to me coming from linux, where several fs can co-exist, as you may know.
if sdcard had its own partition like you say, and it could be formatted to fat, it would suck from a performance point of view, right? because its way slower than ext4 or yaffs2?
sent from my i9250
bk201doesntexist said:
sure, i was talking about nand storage. still, if apps really depend on that to survive (said "fat compability"), it's unlogical to me coming from linux, where several fs can co-exist, as you may know.
if sdcard had its own partition like you say, and it could be formatted to fat, it would suck from a performance point of view, right? because its way slower than ext4 or yaffs2?
sent from my i9250
Click to expand...
Click to collapse
Sure, Android knows how to read/write fat as well as ext. But I guess the app devs figured sdcards would be fat forever. so they only included fat I/O in their apps.
Yes, ext4 is better than fat. But fat+mass-storage is far better and faster than ext4+fuse+mtp. For example, an sdcard backup from fat mounted as mass storage to a pc is much faster and more reliable than an sdcard backup using mtp. MTP backups are painfully slow and often won't even complete due to errors.
strumcat said:
Sure, Android knows how to read/write fat as well as ext. But I guess the app devs figured sdcards would be fat forever. so they only included fat I/O in their apps.
Yes, ext4 is better than fat. But fat+mass-storage is far better and faster than ext4+fuse+mtp. For example, an sdcard backup from fat mounted as mass storage to a pc is much faster and more reliable than an sdcard backup using mtp. MTP backups are painfully slow and often won't even complete due to errors.
Click to expand...
Click to collapse
Well it still happens in 2017 running Android 7.1.2 lol
Sent from my SM-G930W8 using Tapatalk
Hi all,
After searching on the net and a bit of thinking, I have an idea about fully swapping the SD card with internal storage.
In my concept, I will divide the SD card into 2 partitions:
- 1 FAT32 partition for compatibility with other apps and the device itself
- 1 EXT4 partition for swapping
Then, I will inject a small code to the system to run during boot (I think I will use init.d) to unmount /data partition (I don't know if it's necessary) and remount it to the EXT4 partition.
The best part of this method is it's simple, more efficient than Link2SD (since it makes the /data partition gets fully hooked into SD card in no time) and also makes boot up progress faster (no apps check and relink)
If someone can help improving the concept or even turn it into a prototype or a real stuff, leave your ideas at the comments.
Thanks.
too good if this can really be implemented... if someone knows how to do it...please comment
Instead of mounting the sdcard as Data Partition, i would instead Turn of the sdcard Emulation, since the sdcard has lower rw Speed what would slow Down the Phone.
adi2500 said:
Instead of mounting the sdcard as Data Partition, i would instead Turn of the sdcard Emulation, since the sdcard has lower rw Speed what would slow Down the Phone.
Click to expand...
Click to collapse
In fact, the internal EMMC storage is even slower than a SD card. Plus the sdcard emulation is a function implemented into Android kernel itself, while I'm just adding the code. And this is NOT for speed, it's for storage.