I was using "search" to find similar question but i didnt found anything.
My question is :
So far the biggest problem with battery , and android speed was related
with using SD Card.
Ok . I'm a NOOB with Android so don't laugh please :
Is there a way to build WM Rom with smallest number of files
to make device bootable and implement into this Android files ?
I know ... Android is building a BIG folder ( aprox. 700 MB ).
But if we could keep only most important system files
inside the rom , and all the rest will be kept on memory card ???
What you think ?
Is it possible ?
It could save battery , mayby more speed - only if it possible
??????
Still learning - sorry for bad EN.
klopikxda said:
I was using "search" to find similar question but i didnt found anything.
My question is :
So far the biggest problem with battery , and android speed was related
with using SD Card.
Ok . I'm a NOOB with Android so don't laugh please :
Is there a way to build WM Rom with smallest number of files
to make device bootable and implement into this Android files ?
I know ... Android is building a BIG folder ( aprox. 700 MB ).
But if we could keep only most important system files
inside the rom , and all the rest will be kept on memory card ???
What you think ?
Is it possible ?
It could save battery , mayby more speed - only if it possible
??????
Still learning - sorry for bad EN.
Click to expand...
Click to collapse
There are no drivers for the NAND as far as I know. That is why there is SD boot. Go to a file explorer in android and there is no nand partition or folder in the root alongside 'sdcard'
so from what i understand, we need windows booted to power up all the hardware. correct?
i think what he was asking and i was asking earlier is:
if we build a minimal windows boot, ONLY to power up the hardware, and then move the "android" folder from memory card to main phone memory and create the launcher to start the haret and the other file from the phone memory just like it would start from SD card.
in other words treat the phone memory like a SD card am i missing something?
fuzzysig said:
so from what i understand, we need windows booted to power up all the hardware. correct?
i think what he was asking and i was asking earlier is:
if we build a minimal windows boot, ONLY to power up the hardware, and then move the "android" folder from memory card to main phone memory and create the launcher to start the haret and the other file from the phone memory just like it would start from SD card.
in other words treat the phone memory like a SD card am i missing something?
Click to expand...
Click to collapse
That is right !!!
But not to move everything from catalogue Android from SD card to phone memory.
Only most necessary files like drivers, kernel and such.
Files that could keep battery lives longer on stanby with good system stability.
If not possible...... maybe your way will be better ...if possible.
well to split the filesystem between main memory and sd card you have to change alot of file refferences and links its gonna be a nightmaire.
but i dont know enough about this system to tell if this could work or not
Ladies & gentlemen;
Good day!
Well, I am one of those who admire the XDA BIG TIIIMMEE!! However I have an HD2 and managed to have it as a NAND Android after the help of the XDA (as usual of course!) Anyway when I started looking for new ROMs I have noticed that there is new method or way which I do not grasp, comprehend and assimilate AT ALL....ZIP that is, such as [A2SD+], NAND SD and ClockworkMod.Recovery!!!
What is the difference between running Android on NAND & SD with ClockworkMod?!
I am sorry people because truly I must have missed threads or the way of understanding, so hopefully you'll going to be the teacher of mine for now and always!
Could anyone help me as if I am 7 years old?!!!
THANK YOU XDA & Members!!!!
Android nand is running off internal memory. Sd option is what it says, a build running off your sd card opposed to running it with nand.
Thank you for your explanation, but does that mean if the Android runs off internal memory would make the running proccess faster or it would hepl smoothen applications response?! What is the use if I already have the internal memory, wouldn't be even better off?!
Hello
SD Builds start to boot from SD card while being on WM6.5. The hardware shutsdown WinMo and runs Android on it.
NAND Builds run from the internal memory of the phone(just like where WinMo was before)
RAM Builds load all the OS from the SD Card inside the RAM.
[A2SD+] means that you can use a small ext2,ext3 or ext4 partition in your SD Card for increasing your internal storage memory for installing more apps... so this means more internal space.
ClockworkMod is a small linux-based booting utility allowing users to install Android Builds on-the-go which are stored as zip packages on the SD Card. It allows you to install new kernels as update.zip packages as well without having to re-format your entire phone again, or just to erase all personal data on the sd-ext partition.
So, in fact a lot of things have changed in the last 3 months... these are just a few features i can tell you about every method, but at least I hope this will help you to understand quickly a bit about all that.
You know!!?? I Thank you all guys!!!!
NAND runs off the internal memory and even though you get much lower Quadrant scores, NAND is much more responsive and smooth.
The only reason SD based builds get more Quadrant is because of I/O speeds thanks to the SD card.
SD builds are fast, but NAND builds are much SMOOTHER and reliable and if you can do something on SD, you can do it just as well on NAND (gaming for example).
Hi installed wp7+Android using dual boot with magldr1.3
now i'm very satisfied with Android, and want to install a new build of wp7 without toutching Android ! how to do? if i install wp i think i will damage android partition in my SD card plz help
regards
+1
That is correct, if you reinstall WPH it will (re)format your SD card and so erase the Android partition.
But some guys here will surely provide the anwser to that problem.
hica said:
Hi installed wp7+Android using dual boot with magldr1.3
now i'm very satisfied with Android, and want to install a new build of wp7 without toutching Android ! how to do? if i install wp i think i will damage android partition in my SD card plz help
regards
Click to expand...
Click to collapse
Should be easy, in theory at least.
1. Use a disk imaging software to make an image of the entire partition you use for Android and save that image on your computer.
2. It'll perhaps be a good idea now to delete the Android partition or better yet, delete both WP7 and Android partitions altogether and make just one FAT32 partition spanning the entire card. This might not be necessary but it'll give the next step a stock, empty, Fat32 formatted SD card to begin with.
3. Install the new WP7 build.
4. Go through the entire process of setting up the partitioning for dual-booting the way you did it in the first place with your previous setup.
5. Once you have the Android partition resized and formatted...simply write the disk image saved from step 1 to it using your favorite disk imaging software.
Please note that I have NOT tried this out and can't confirm if it'll work but in theory, it should. Also, if you keep the partitions exactly of the same size that you had in the first place with your original dual-boot setup, it'll *probably* increase the chances of it working in the end.
Hope it helps. =)
I agree with HQRaja.
I would simply create a folder on your Desktop and call it Android Partition Backup, or something simular. Insert the memory card and only the Fat32 partition will be visable in Windows so select everything and move it to the newly created folder on your Desktop. Install Sd Formatter from here. Once launched click on options, Format Type as Full Erase, Format Size Adjustment as On then OK. This will format not only your fat32 partition but remove all partitions as well. Then install the new WP7 Rom, Dual Boot as before and then copy everything from your backup folder back onto your card.
If you feel you dont have enough room for music, apk's or want to try mulitple Android Roms while still using WP7, the keep an eye out for my new tutorial where you can have say over 11gb for Adroid and over 3gb for WP7. It is written out but will read it through more tomorrow to make sure it is ok before uploading. I would do it tonight except my Mrs is nagging and I have been summond .
Hope this helps.
I have been searching for a solution where I can increase/allocate 75% space in sd card for android use and the remaining for w7. I heavily used android because of more games and applications. I am using w7 just for show
Hello,
i'm quiet new to use Android Build on HD2. So far i used SD Builds and NAND Builds.
Can anybody help me understand the Pros And Cons of each configuration ?
I mean i would like to understand :
1. What is the less battery consuming configuration (SD Builds, APP2SD, with 2 partitions ? with 3 partitions ? RAM Builds)
2. What is the configuration that provides the best performances ?
PS: for information i have a Leo 512 with an micro SD 16GB class 10
Ok,
SDcard builds use more battery as it's constantly accessing the card.
Apps2sd moves some of your applications to a partition on the sdcard (You have to create this partition yourself) to save room on the phone's memory, as if you use a lot of apps you can fill up the memory on the phone. It uses some extra battery power, but not constant
number of partitions doesn't matter.
RAM builds is the only decent option in terms of battery usage, also it has the best developers working on NAND roms (in my opinion, sorry if that upsets anyone)
You'll have to try different builds yourself to find out which works best, I've seen NAND builds that empty your battery in less than a day and some that seem to last days, with the same 'configuration'
As with everything on this forum, you need to TRY things for yourself. Just make sure you have HSPL installed
Good luck
Many thanks for your info it helps a lot !
Hey Guys,
I asked @kokotas to help me figure out a way to make a Patch to extend the Internal Memory as for me, due to the size of the high-end Applications and Games, is too limited 16GB, 11,70GB available only, on our Z1.
So my first Idea was to sacrifice 16Gb Internal Memory and use 64GB External SD Memory formatted in EXT4 where all the Data will be stored.
To do so we have to understand few thing and how is the structure of the Z1 Kernel is made and try to extract "ramdisk.cpio" where we can edit "init.rc" and change the line "/data mount"
As for the kernel "Autopsy" we used @krabappel2548 kernel build, I hope he is fine with that.
From what we know, the recovery is injected in the boot.img and this makes things more complicated.
Are all kernels built in this way? Even the stock ones?
Also, is there a specific rule in the way of naming the included ramdisks?
I attached a picture to make things more clear.
Any help will be appreciate.
eclyptos said:
Hey Guys,
I asked @kokotas to help me figure out a way to make a Patch to extend the Internal Memory as for me, due to the size of the high-end Applications and Games, is too limited 16GB, 11,70GB available only, on our Z1.
So my first Idea was to sacrifice 16Gb Internal Memory and use 64GB External SD Memory formatted in EXT4 where all the Data will be stored.
To do so we have to understand few thing and how is the structure of the Z1 Kernel is made and try to extract "ramdisk.cpio" where we can edit "init.rc" and change the line "/data mount"
As for the kernel "Autopsy" we used @krabappel2548 kernel build, I hope he is fine with that.
From what we know, the recovery is injected in the boot.img and this makes things more complicated.
Are all kernels built in this way? Even the stock ones?
Also, is there a specific rule in the way of naming the included ramdisks?
I attached a picture to make things more clear.
Any help will be appreciate.
Click to expand...
Click to collapse
1. Sony doesn't have a recovery partition in their phones hence developers add the recovery in the ramdisk. Also stock sony kernels doesn't have a recovery included by default only bootloader/flashmode.
2. You can't adjust the 16gb internal partition without diving deeply into the bootloader. The NAND partition profiles are hardcoded in the bootloader so modifying even just a little bit of info in the partition of the NAND would brick your device. The only way I could possibly suggest to try is hijacking the fstab and ramdisk to unmount the internal storage and mount the external storage on init. But if your issue is only about disk space I suggest you leave the internal storage and just symlink the obb folder instead of hijacking the whole internal storage. And BTW the disk IO of the internal storage is worlds apart compared to your microsd card no matter what class it is so it would be very unefficient if you use your microSD card as internal. IMHO reading the dalvik-cache 1 by 1 on startup would be pretty slow! Same goes for reading the byte code of an app once you open it.
Riyal said:
1. Sony doesn't have a recovery partition in their phones hence developers add the recovery in the ramdisk. Also stock sony kernels doesn't have a recovery included by default only bootloader/flashmode.
Click to expand...
Click to collapse
We know that. If there will be a Partition for recovery it will be much more easy and safe. That why we also used a Kernel with recovery implemented.
Riyal said:
2. You can't adjust the 16gb internal partition without diving deeply into the bootloader. The NAND partition profiles are hardcoded in the bootloader so modifying even just a little bit of info in the partition of the NAND would brick your device.
Click to expand...
Click to collapse
We trying and this is the risk of everybody who flashing a Custom Kernel.
Riyal said:
The only way I could possibly suggest to try is hijacking the fstab and ramdisk to unmount the internal storage and mount the external storage on init. But if your issue is only about disk space I suggest you leave the internal storage and just symlink the obb folder instead of hijacking the whole internal storage.
Click to expand...
Click to collapse
Maybe not the whole internal storage but implement the external SD with the internal?
Riyal said:
And BTW the disk IO of the internal storage is worlds apart compared to your microsd card no matter what class it is so it would be very unefficient if you use your microSD card as internal. IMHO reading the dalvik-cache 1 by 1 on startup would be pretty slow! Same goes for reading the byte code of an app once you open it.
Click to expand...
Click to collapse
I know the difference between Internal and External Storage. Yes the internal bandwidth is higher but like I said is worth the sacrifice, or try. Best solution will be System and Apk on Internal and link the SD to use there all Data. This is more efficient that a third Apps like Link2sd or kind of. BTW, I don't think it will be so slow but we have to try. The idea have to be made to improve what next.
So we need more Ideas, do you have any?
We know that. If there will be a Partition for recovery it will be much more easy and safe. That why we also used a Kernel with recovery implemented.
We trying and this is the risk of everybody who flashing a Custom Kernel.
A: This isn't about risk this is a fact. Once you successfully manage to alter the partition table of the built in NAND you're sure to get a hard brick from doing this.
Maybe not the whole internal storage but implement the external SD with the internal?
A: Implementing internal storage with external to support it is possible but limited. Like I said you could symlink the obb and Android folder to the external storage. That way you can allocate some of the storage space to data, dalvik etc. and the data files to the external SD which uses the most resources.
Hmm, changing the partition table has been successfully done on the xperia T
http://forum.xda-developers.com/showthread.php?t=2147997
I am not an expert here, but is this what you are talking about,
What benefit would this give a user?
Sent from my C6903 using xda app-developers app
gregbradley said:
I am not an expert here,
Click to expand...
Click to collapse
Me either, @kokotas is the Master here and all thanks should go to him for help me with this, actually the picture is of his work.
gregbradley said:
Hmm, changing the partition table has been successfully done on the xperia T
http://forum.xda-developers.com/showthread.php?t=2147997
Click to expand...
Click to collapse
We do not try to repartitioning the Sony Z1 internal memory to get a recovery bootable from different partition, which still a very good idea to develop for Z1. We try to mount the External SD instead of the Internal to expand the storage for the Z1, and here we need a patch. If kind of patch like that will really work, with some help, anyone just will format the SD in EXT4 and use what like he like, 32/64GB.
So we will be glad even to involve more "Programmers" to help us make it true.
So any way to let this work?
Jay794 said:
What benefit would this give a user?
Click to expand...
Click to collapse
Expand storage. You will be able to format a 64GB, micro SD in 2 Partitions and use 32GB by the System and 32GB like a normal SD, for example, and it will be managed by the system and not by Apps. So instead of 11,70GB you will have 30GB in System.
Surely this will just make accessing the SD card data really slow? Even with a class 10 running games off the SD card would be laggy as hell
Sent from my C6903 using xda app-developers app
Jay794 said:
Surely this will just make accessing the SD card data really slow? Even with a class 10 running games off the SD card would be laggy as hell
Click to expand...
Click to collapse
Thank you for your Opinion. Is not your problem.
Expert Request Please..
Can someone who know more than me just have a look on the attachment and answer few question, unanswered form post 1.
..for Z1
1) Are all kernels built in this way? Even the stock ones?
2) Also, is there a specific rule in the way of naming the included ramdisks?
3) Do all kernels use the sbin folder?
4) Is ramdisk.cpio the default name used in all kernels
Hey, I support the idea, I just don't see how useful it will be
Sent from my C6903 using xda app-developers app
gregbradley said:
Hmm, changing the partition table has been successfully done on the xperia T
http://forum.xda-developers.com/showthread.php?t=2147997
I am not an expert here, but is this what you are talking about,
Click to expand...
Click to collapse
Yes it is possible but not easy... I'm pretty sure the dev that made that had a hard time before he successfully got it. Also I'm pretty sure he has a JTAG box so in case his phone got hard bricked he can easily fix it again. Also IMHO that was already patched by sony on the latest s1boot so I'm sure it's alot harder than before.
Riyal said:
Yes it is possible but not easy... I'm pretty sure the dev that made that had a hard time before he successfully got it. Also I'm pretty sure he has a JTAG box so in case his phone got hard bricked he can easily fix it again. Also IMHO that was already patched by sony on the latest s1boot so I'm sure it's alot harder than before.
Click to expand...
Click to collapse
Yes, he did brick his Xperia T a few times, and the LK kernel was never really taken up because of the risks.
But it does show that it was possible to change the partition table.
As for on the xperia Z1, I don't know
gregbradley said:
Yes, he did brick his Xperia T a few times
Click to expand...
Click to collapse
I can do that.
Only problem with having the SD used all the time for system files is the risk of corruption and or a failed card.
Saying that I had it on the S3 and it worked brilliantly, was a relatively simple script which required init'd support from a custom kernel.
In all fairness, after using folder mount the worries i've had with my internal memory have gone, i'm always over 10GB of space with several really big games installed which would easily take over the whole internal memory.
dladz said:
Only problem with having the SD used all the time for system files is the risk of corruption and or a failed card.
Click to expand...
Click to collapse
Here you sound like Google.
dladz said:
Saying that I had it on the S3 and it worked brilliantly, was a relatively simple script which required init'd support from a custom kernel.
Click to expand...
Click to collapse
I had it on HD2 as well and never had any issues and I had full control of my device, this is what also we looking at, no restrictions and no storage limit on a high-end device. I will be glad to see 64GB recognized as my System Storage instead using Apps on Apps like the Mount Folder.
I play Most Wanted, of curse a bit slow, on mine HD2 so if we get this work we will have 40mb/s in writing and reading, instead of 70mb/s in internal, due to the limitation of the slot. I think even with a kind of transfare like that you will never see any slow down of the performance on your device.
Some Smart One will say now to me "Why then you don't go back to HTC". That's the point! Imagine have Z1 with such a Development and full control of you device.
At last it's a choice of the user if he want apply that patch or not, but I think if this will be possible many will be happy, but like I can see, we don't have much support due to the risk and any Developer will not take this in consideration, or maybe will, but apparently not now.
eclyptos said:
Here you sound like Google.
I had it on HD2 as well and never had any issues and I had full control of my device, this is what also we looking at, no restrictions and no storage limit on a high-end device. I will be glad to see 64GB recognized as my System Storage instead using Apps on Apps like the Mount Folder.
I play Most Wanted, of curse a bit slow, on mine HD2 so if we get this work we will have 40mb/s in writing and reading, instead of 70mb/s in internal, due to the limitation of the slot. I think even with a kind of transfare like that you will never see any slow down of the performance on your device.
Some Smart One will say now to me "Why then you don't go back to HTC". That's the point! Imagine have Z1 with such a Development and full control of you device.
At last it's a choice of the user if he want apply that patch or not, but I think if this will be possible many will be happy, but like I can see, we don't have much support due to the risk and any Developer will not take this in consideration, or maybe will, but apparently not now.
Click to expand...
Click to collapse
I actually probably will be going back to HTC after this phone. Doubt it'll be the M8, although i do like it, the camera is sup par though and i've come accustomed to a decent picture.
dladz said:
I actually probably will be going back to HTC after this phone. Doubt it'll be the M8, although i do like it, the camera is sup par though and i've come accustomed to a decent picture.
Click to expand...
Click to collapse
I know, I try to don't give up on it too but to much to deal with. The camera is good but I was disappointed anyway. So I was thinking about 64GB HTC One, or wait for the next release and I will finally be fine. For the moment I try to deal with Z1, I hope somewhere we will have 64GB system storage , this maybe will change my mind, everything is possible.
eclyptos said:
I know, I try to don't give up on it too but to much to deal with. The camera is good but I was disappointed anyway. So I was thinking about 64GB HTC One, or wait for the next release and I will finally be fine. For the moment I try to deal with Z1, I hope somewhere we will have 64GB system storage , this maybe will change my mind, everything is possible.
Click to expand...
Click to collapse
Have you used folder mount before? It really is a great app and i've not needed the larger internal storage since using it.