Hello i have test a new solution for more stability more speed and no bug when i extract my sd card.You must copy on the internal memory in folder just 4 files "zimage,startup,haret,clrad" then launch clrad and haret and let's rock.
And can you boot android with no sd card ?
Of course not, there is no system on internal memory. Thats why he called it semi-nand. Not sure if it has any benefits at all though.
So basically it is something like lauch from sd but runs from nand.
maybe less power consumption?
better consumption,just the kernel in internal memory work whitout sd card after launch.Be carful you can extract your card but you can't launch any apps
There will be no difference! The zImage (kernel) is completely loaded into RAM and other files are required to load and run the zImage...
rkalas said:
There will be no difference! The zImage (kernel) is completely loaded into RAM and other files are required to load and run the zImage...
Click to expand...
Click to collapse
This is correct. There will be absolutely no difference as once Android is running, the kernel is loaded to RAM anyway, regardless of where it is stored.
there is nothing to do with nand for this method, unless the data.img able to store in nand.
test this method ,the boot is fast and your system is more stable and some bugs desappear.when you listen music and you copy a file with root explorer in the tmp folder for exemple the music stop not whith this method.Try before
Related
Hey guys,
I'm going to try making an Android ROM. It will be a bare-bones WM ROM with the necessary Android files built in.
It will run Haret at start up, but you have the choice to not run it if you don't choose to. (in case Android acts up).
I'm booting up Android right now from my ROM (not SD card).
I'll let you guys know how it goes
PLEASE REPLY WITH THE SIZE OF YOUR DATA IMAGE!!!!
awesome, sounds good.
I'm definitely game. Let us know when you've got it up!
How big is everyone's data file?
i just wanna be clear on what you're doing here. so, you could take your SD card out and still run android, correct?
regardless, this isn't really an android ROM. it's just a slim windows ROM. the only speed-up i could see, would be when winmo is loading up. once haret begun, it should be the same speed as we're currently used to.
data.img is 128mb.
128 MB here
128 Mb for me!
Okay, I think they are all set to 128MB, and then say how much is free. Right now it has space for the 128MB.
I am going to make it copy the files from the SD card to /Program Files/Android, and then have Haret start (with the option to run or not).
I am not seeing a super large speed boost, but it is a little faster, and seems to be more stable.
craig0r said:
i just wanna be clear on what you're doing here. so, you could take your SD card out and still run android, correct?
Click to expand...
Click to collapse
Correct
craig0r said:
regardless, this isn't really an android ROM. it's just a slim windows ROM. the only speed-up i could see, would be when winmo is loading up. once haret begun, it should be the same speed as we're currently used to.
Click to expand...
Click to collapse
It is a little faster (since it isn't using the SD card), and is a lot more stable for me.
Would it be feasible to run a script in WinMo to check to see if there is a newer version of the android files and prompt to update them if the files are newer?
what filesystems are you using for the system and data? Are you using file-backed storage or direct access to the memory device? You won't see as much of a speedup if you are using file-backed storage...
You also will want to modify initrd to change the memory settings, I can do that for you if you like...
derekwilkinson said:
Hey guys,
I'm going to try making an Android ROM. It will be a bare-bones WM ROM with the necessary Android files built in.
It will run Haret at start up, but you have the choice to not run it if you don't choose to. (in case Android acts up).
I'm booting up Android right now from my ROM (not SD card).
I'll let you guys know how it goes
PLEASE REPLY WITH THE SIZE OF YOUR DATA IMAGE!!!!
Click to expand...
Click to collapse
Are you putting a yaffs2 partition on the nand flash for data or using a loop mounted file on top of tfat. How about the system image? There should be a significant speedup from using the nand flash. Also, how are you passing the partition information to the kernel?
craig0r said:
regardless, this isn't really an android ROM. it's just a slim windows ROM. the only speed-up i could see, would be when winmo is loading up. once haret begun, it should be the same speed as we're currently used to.
Click to expand...
Click to collapse
True, it isn't an android rom... but most of the slowness we're experiencing is due to a slow bus interface to the SD card, and slow write speeds to the SD.
If properly accessing the internal memory, there should be significant speed increases.
EDIT: By the way, if you are just using an ext2 data.img sitting on the tfat partition, you are likely to see bad things happen to your internal memory.
ext2 doesn't do wear leveling, and the internal flash controllers also don't do wear leveling. TFAT is set up to do it, but if you are just reading it as FAT, it won't do it... you want to access the memory directly and set up a yaffs2 partition.
vilord said:
what filesystems are you using for the system and data? Are you using file-backed storage or direct access to the memory device? You won't see as much of a speedup if you are using file-backed storage...
You also will want to modify initrd to change the memory settings, I can do that for you if you like...
Click to expand...
Click to collapse
Honestly, I just made a super small ROM so it could run the Android files more stable (since it isn't on the SD card).
How can I have direct access to the memory device?
well to start, how do you get to the files now?
I'm going to guess that you turned on kernel support for the internal memory, which makes it show up like a block device, then you are mounting the windows TFAT userdata partition, then mounting system.img and data.img as loop.
What you would do for direct access isn't all that different...
Right now you have a *very* small windows rom, which leaves a large space for userdata. You'd need to force the tool to leave an open space at the end of the flash, then you'd use a linux tool to mkfs.yaffs in that open space. It is similar to a hard disk (with a different partition table), except that you want to use yaffs or jffs2 to enable wear leveling.
vilord said:
well to start, how do you get to the files now?
I'm going to guess that you turned on kernel support for the internal memory, which makes it show up like a block device, then you are mounting the windows TFAT userdata partition, then mounting system.img and data.img as loop.
What you would do for direct access isn't all that different...
Right now you have a *very* small windows rom, which leaves a large space for userdata. You'd need to force the tool to leave an open space at the end of the flash, then you'd use a linux tool to mkfs.yaffs in that open space. It is similar to a hard disk (with a different partition table), except that you want to use yaffs or jffs2 to enable wear leveling.
Click to expand...
Click to collapse
I took a Vogue ROM, stripped everything out, and copied the Android files from my SD card to the device.
Did you change the initrd and zImage at all? I would think you'd need to change them to tell the loader to look at the internal memory instead of looking at the SD card...
soo when will this rom be ready? also will the base system be winmo 6.1 or 6.5?
fixxxer2008 said:
soo when will this rom be ready? also will the base system be winmo 6.1 or 6.5?
Click to expand...
Click to collapse
When I get everything running as fast as possible.
I'm about to write the scripts to make everything work easier
(like copy your current default.txt and data images to the device so you keep your data) and maybe automatic updates (haven't decided how i'll make it work yet).
I will apologize if this has been asked before. But I have been search for while and still have no clue.
The situation is: I normally run android with haret on sdcard without partition. (Thanks to all the developers). Every build is very fast except the most recent mssmison eclair (the new way). So, I tried to run the mssmison eclare on sdcard with partitions. It turns out to be even slower. I then tried most of the other releases which were fast without partition. All of them became very slow on partitions.
I guess it is possibly because I have a sd card without any "class x" label, (maybe class 2). But anyway, shouldn't android be faster with partitions than w/o?
or is there something related to permission fix?
Here is my settings:
Htc vogue
3 partitions: fat32+ext2(system)+ext2(data), I also tried fat32+ext2(system)+ext2(data)+swap, all very slow
Thanks
make sure you are choosing the right options in the installer. if you have system.img and data.img in your /andboot folder, then you are not running off the ext2 partitions and choosing the wrong default install location options.
tatnai said:
make sure you are choosing the right options in the installer. if you have system.img and data.img in your /andboot folder, then you are not running off the ext2 partitions and choosing the wrong default install location options.
Click to expand...
Click to collapse
After install , I have no sytem or data in my /andboot or /android folder. The system is renamed and moved to a backup folder by the installer. with the new way, I can choose where to put the system and data, "system on sdcard" and "data on sdcard", which are default, are selected.
Yes I also noticed that Eclair wasn't running fast even though I was using two Ext2 partitions. I didn't notice any speed difference between having the files stored directly in the android folder as opposed to Ext2.
definitely thought I noted a speed increase running on ext2 instead of regular sd card.
i really wana know which partition is better ext 2 3 or 4? n also if u can move songs etc to the partitioned space??
Hey everyone.
I installed a leaked version of Froyo on my Galaxy 3 I5800. I'm using the hack to always install the apps on the memory card. However, only the main apks of the apps are being stored on the memory card. Any application data is still being stored on the internal memory. For example, installing Angry Birds takes 10 MB on the memory card, but also takes about 2 MB on the internal phone memory..
Apps2SD is a huge improvement, but still, if the data's being stored on the internal memory, I'm gonna run out of space some time or the other.
Is there a hack or something to make the phone keep even the data on the memory card? I've heard about Apps2Ext but not sure if that can be installed on my phone and whether it stores the app data on the EXT partition too.
Any ideas?
Android documentation says that even when app. is installed on SD card,
"The .apk file is saved on the external storage, but all private user data, databases, optimized .dex files, and extracted native code are saved on the internal device memory."
TekkenLaw said:
Android documentation says that even when app. is installed on SD card,
"The .apk file is saved on the external storage, but all private user data, databases, optimized .dex files, and extracted native code are saved on the internal device memory."
Click to expand...
Click to collapse
May be that's better because program can run faster.. anyway you can solve it by creating of ext2 partition on your SD card and virtualy enlarge internal storage.
But I haven't found any manual how to do it on i5800.
Are there ext2 capabilities in the i5800's Froyo? I'm asking because 2.1 lacks them, much to my dismay. A Linuxish device with a closed file system (rfs) with no tools available (and FAT), erm...
addicted2088 said:
Hey everyone.
I installed a leaked version of Froyo on my Galaxy 3 I5800. I'm using the hack to always install the apps on the memory card. However, only the main apks of the apps are being stored on the memory card. Any application data is still being stored on the internal memory. For example, installing Angry Birds takes 10 MB on the memory card, but also takes about 2 MB on the internal phone memory..
Apps2SD is a huge improvement, but still, if the data's being stored on the internal memory, I'm gonna run out of space some time or the other.
Is there a hack or something to make the phone keep even the data on the memory card? I've heard about Apps2Ext but not sure if that can be installed on my phone and whether it stores the app data on the EXT partition too.
Any ideas?
Click to expand...
Click to collapse
install move to SD first then choose the option Exteral SD.Anything you install from now on will be installed to the SDCARD but aware the widgets and programs that require root doesn't work well in the SDCARD together with home replacement program.Unless of course the app itself support installing to SD.
banahaw said:
install move to SD first then choose the option Exteral SD.Anything you install from now on will be installed to the SDCARD but aware the widgets and programs that require root doesn't work well in the SDCARD together with home replacement program.Unless of course the app itself support installing to SD.
Click to expand...
Click to collapse
this is what he did. But not everything will be saved to SD. This is the what he says.
nastyba said:
this is what he did. But not everything will be saved to SD. This is the what he says.
Click to expand...
Click to collapse
Yeah, the APK file, that is the main package, is installed on the SD card. However, all the data that the application actually saves are usually on the internal device memory.
I have enabled Move to SD and set the install path to external, but it will still save application data on the phone memory. That is how Android is designed to work
banahaw said:
install move to SD first then choose the option Exteral SD.Anything you install from now on will be installed to the SDCARD but aware the widgets and programs that require root doesn't work well in the SDCARD together with home replacement program.Unless of course the app itself support installing to SD.
Click to expand...
Click to collapse
Oh yes, I'm aware of all this. But still wanted to mention the point that the internal memory will always get used..
addicted2088 said:
Oh yes, I'm aware of all this. But still wanted to mention the point that the internal memory will always get used..
Click to expand...
Click to collapse
you can extend your internal storage with your SD card, but you need to create ext2 partition on your SD card first and then <i>and this is the problem</i> explain to your i5800 to use this partion on SD card.
I've red many articles about it on HTC / SE phones where this method work. They say that the ROM must be customized, which haven't been done yet with our phone. The problem is, that the good programmers have Desire / or SGS and they do not care about the i5800
nastyba said:
you can extend your internal storage with your SD card, but you need to create ext2 partition on your SD card first
Click to expand...
Click to collapse
And this is where the problem starts: The i5800 cannot handle ext2, at least not with its stock roms. You're stuck with an exotic proprietary file system (rfs) for which no tools are available.
mizch said:
And this is where the problem starts: The i5800 cannot handle ext2, at least not with its stock roms. You're stuck with an exotic proprietary file system (rfs) for which no tools are available.
Click to expand...
Click to collapse
may be one day there will be a custom rom which will allows it
nastyba said:
may be one day there will be a custom rom which will allows it
Click to expand...
Click to collapse
mizch said:
And this is where the problem starts: The i5800 cannot handle ext2, at least not with its stock roms. You're stuck with an exotic proprietary file system (rfs) for which no tools are available.
Click to expand...
Click to collapse
Is this problem allready solved?
Because my bro has problems with the little internal space.
(•.•) said:
Is this problem allready solved?
Because my bro has problems with the little internal space.
Click to expand...
Click to collapse
Yes. For that you need to first flash a fugumod kernel. Then you can use Kyrillos' apptosd script from here. You need to use apptosd script v3 if you want your /data/data to be transferred to your SD. But script v3 works good only with class 6 SD card or higher.
Oh yes. You need to convert your data partition to ext4 and create an ext4 partition in SD card also.
ok formating...
seems that i have here a class 4 sd card 8gb... damn it!
I am currently on Kyrillos 6.1. If i create an EXT4 partition in my SD card, via CWM recovery, how can i move the apps which are already installed in my phone memory to that partition? Like if i use Titanium backup, then would moving the apps would go to FAT partition or the newly created EXT4 partition?
mrn123 said:
I am currently on Kyrillos 6.1. If i create an EXT4 partition in my SD card, via CWM recovery, how can i move the apps which are already installed in my phone memory to that partition? Like if i use Titanium backup, then would moving the apps would go to FAT partition or the newly created EXT4 partition?
Click to expand...
Click to collapse
First backup your apps using titanuim backup. It will get backed up in SD card. Then copy the backed up apps and the rest of the stuff in your SD card to your PC. Then goto recovery, advanced, partition SD card. Create the required partitions. All data in SD card will be erased. Then in recovery only, wipe data. Then reboot. After that all the apps which you install will goto the ext partition that you created.
Thanks Dhiren!!! I was just wondering whether there was any way to directly move the apps to the EXT4 partition which are already installed on phone memory..I shall try out as you said...
When it comes to installing apps on HD2 Android ports.
Is it faster for Android to read/write files directly from/on SDcard than from internal memory
Becouse internal memory in our case is data.img file. So we are writing "Files" inside the data.img file.
Makes more sense to use SD card for installing application. Less processor work.
This is just my thinking. I want other optinions on this.
Yes, you're right. It's quicker to install the files in the /sdcard/ folder than inside a compressed file.
johncmolyneux said:
Yes, you're right. It's quicker to install the files in the /sdcard/ folder than inside a compressed file.
Click to expand...
Click to collapse
Using Neopeek EXT2 partition on my TD2.
hah, finally we have something you dont have on HD2
Hi,
I have installed NAND Android on my "Singaporean" HD2. After installing just few applications i got a message about low space and U found that the internal storage is 150MB only!!! How come?
I tried App2SD but still nothing happened since most imortant apps LOVE the internal storage.
Is it possible in anyway to install a new & larger internal storage?
Is it possible in anyway to install Android into the SD without having anything in the internal storage (Without having WinMo)?
Thanks,
Mohammad
Try one of these NAND builds:
RAFDROID HD or imilkas' HD2Z NAND
These builds will store the data.img on SDCard. If you use the same type of build (stock, desire, desire hd,cyanogen..), it is possible that your old data.img from sd build will working. If you have problems, put a new data.img on sd and restore your apps/settings with Titanium Backup or HTC/Google Sync.
So you mean these build put all my stuff in the SD?
if so then this is great!!
Thanks
Mohammad
Yes, your stuff will be in the data.img on sd, the system is in nand. Because these builds have more space in the Nand, some of them has completely deoxed all system files, so you can customize it with special icons or languages. The deoxed RAFDROID HD rom has for example battery icons with percentage counter.
rafpigna said:
It's fully DEODEXED so you can theme it as you want.
I tried also to keep most of the apps, background and other stuff in it.
But most important it uses DATA.IMG on SDCARD so you dont have to worry about storage limite on LEO512
Click to expand...
Click to collapse
I have found another build with this feature, a MIUI Build.
Advantages of such builds:
- easier backup of complete userdata
- theoretically unlimited userspace (see 4GB working)
- faster write speed at userdata (but slower access time)
Disadvantages:
- slower read speed and higher battery drain at userdata
- battery drain should be between a complete nand and sd
I dont have tested such a rom, I have the Nand gauner build. It has 184MB userspace at start, it is enough for me and works top after some reboot's.
I have enough space left and my big apps have the MoveToSD option, but still not applied.