Okay, I'll be honest... I am very lost. I have been checking in to look at the progress that has been made on the android - vogue project. Apparently though, I have been gone for a little too long.
I'm running zenulator's senseHERO-v1.3.3 from my SD card using haret. I like it a lot however, it is much to slow to use all the time.
I watched jamezelle's video (here) and it look a LOT faster then mine.
I know that the speed has something to do with the way the SD card is partitioned, however... I'm at a loss.
Is there any way that someone would be able to help me get this rom running at the speed in Jamezelle's video?
Thank you, and sorry if this has been posted before.
hi,
i have the same problem. I have a polaris/crise.
i've read using a sd card with 6 class
the speed improves. i did it but the speed
got the same.
So, i have some questions about partition:
- in which partition do i execute haret.
which files do i use and in which partition
should i put them?
- if all 3 partitions (fat32, ext2 and swap)
are from linux, will wm detetec them to execute haret?
thanks a lot!
p.d: sorry for my english
Weird, I never noticed that my phone was slow until I watched jamezelle's video.
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).
As The Title Suggests, Is There Any Way To Install A ROM Onto A 16GB MicrSDHC (class 10) Instead Of The Phones Internal Memory?
I 'Googled" It For Several Hours, Unfortunately Did Not Find An Answer.
Let Me Explain Further As To What I'm Really Trying To Accomplish. I Want To Flash A(ny) ROM Onto The MicroSD Card So I Will Have The Entire Internal Memory Free On My G1. And Then (if at all possible) Somehow Use The Internal Storage As Extended RAM.
Even If This Seems "Close To Impossible", Could Someone With Enough Knowledge (a dev?) Explain How Something Like This "Could" Be Accomplished??
Thanks For Your Time! Can't Wait To Read What People Have To Say About This..
Ideas & Possible Solutions Are Better Than Just Saying 'It Can't Be Done..etc'
As for installing a rom onto sdcard (even on ext2 partition as it is being done on the HTC Fuze/Diamond/Topaz/etc windows series phones), it is completely possible, but it is very slow.. i don't see why you would want to do that even compared to NAND install if you have lots of ram
I used to be a developer for the HTC Fuze (Touch Pro) and made a 2.2 aosp SD-ext rom, it still isn't as fast as the G1 even though it has slightly higher specs: 288 ram, msm7201a (same cpu as htc dream)..
You can't extend the RAM, but you can make it swapspace. It would kill the internal memory very quickly because it is only yaffs and has a limited number of read and writes...
SH31KH said:
As The Title Suggests, Is There Any Way To Install A ROM Onto A 16GB MicrSDHC (class 10) Instead Of The Phones Internal Memory?
I 'Googled" It For Several Hours, Unfortunately Did Not Find An Answer.
Let Me Explain Further As To What I'm Really Trying To Accomplish. I Want To Flash A(ny) ROM Onto The MicroSD Card So I Will Have The Entire Internal Memory Free On My G1. And Then (if at all possible) Somehow Use The Internal Storage As Extended RAM.
Even If This Seems "Close To Impossible", Could Someone With Enough Knowledge (a dev?) Explain How Something Like This "Could" Be Accomplished??
Thanks For Your Time! Can't Wait To Read What People Have To Say About This..
Ideas & Possible Solutions Are Better Than Just Saying 'It Can't Be Done..etc'
Click to expand...
Click to collapse
Google Android rom's or Operating systems have rules and limits, I do know androids 2.2 did not allow system files to run outside /system folder, now it's allowing more as you see lot's of rom's using /ext (linux partitions) I do not know all the limits, but do believe there has to be a part of the rom in internel memory to be able to boot sd-card
hello, posting this feedback/question here as i do not have privileges to post on the actual thread itself.. http://forum.xda-developers.com/showthread.php?t=1434860
i used v1.6 w/o any issues outside the known limitations/bugs. 200/10 w/ 40ad2sdx-a2Recovery.zip @ 4Gb.
i only recently upgraded to v2.0 (i am aware there is v2.1 out, but the issues i list arent addressed in the changelog; plus i havent had time to flash the new version). 300/45 w/ 40ad2sdx-a2Recovery.zip @ 4Gb.
1. every other/random reboot causes the phone process to stop.
2. most (large) apps can not be downloaded fully from google play; the media process stops. trying to clear/stop download managers etc. do not help.
3. videos of the same bitrate/size play slower in mx player as compared to v1.6.
could any of the above issues because i used a larger system partition? i know the cache partition isnt used by the OS. df shows that i have a 250M /system and 115M /sd-ext (with 103M used after clean boot). is this always set at the same size?
if this is actually causing the problem (at least for points 1 & 2); does the remaining size after the system partition get split between data and sd-ext? if so is there any way to increase the sd-ext partition and leave the data partition small as ill be mounting it from sd card anyway?
also, does CWR actually delete the dalvik-cache if using a mounted /data directory from the sd card and not from the nand?
after reading the 40ad2sdx init script that is installed. it renames the nand data partition to sd-ext and mounts the extra partition on the sd card as the new data dir. inside the sd-ext dir it copies back from the new data dir; android system apps and leaves the rest.
i see that this rom makes mention of not needing the cache partition or swap as it uses /dev/block/mtdblock5. which would otherwise be the nand data dir or sd-ext if using 40ad2sdx.
im guessing its either because of an swap as file on this partition or apps that live in and use /dev/block/mtdblock5 for temp writing - is what causes processes to stop (ie. as a result of no more virtual memory or temp write space in the directory where they are launched).
i have since upgraded to v2.1 and reverted back to using a 165mb system partition and 5mb cache partition. which leaves a 240mb /dev/block/mtdblock5.
after using 40ad2sdx, the android apps (?and also swap as file?) take up 108mb; leaving 131mb (im guessing) for temp write space; eg. downloading apps from play.
so far i have no more issues regarding points 1 & 2.
can anyone clear up how the process for swap works with this rom? if it was mostly swap to blame, would have mounting a swap partition have solved the problem in the first place? how exactly does this rom use cache/swap on /dev/block/mtdblock5? is there some general method for some/all apps to offload cache data on android and its an actual growing cache directory and not and actual swap as file? when upgrading to v2.1 i created a swap partition anyway, would there be any benefit if i was to swapon this?
re: point 3.
this has not changed. videos of same bitrate still play slower. i also forgot to mention that apps like (guitar) solo lie, real drums and piano perfect also play slower (and are more or less now unplayable, unlike v1.6 where they played fine). i was assume this has something to do with the HWA, has this caused some problem with audio processing?
Did you flash v2.1 with fresh install? (Task29 etc.)
Check my installation here (I have no issues).
Could you tell us a parameters of your memory card? We also have seen that one HD2 can behave different than another
NexusHD2 is not using SWAP partition, so creating it has no point. Maybe you should use a smaller partition size if you have enough space. I used 512MB and i still have 200MB free after install all my apps. Rest of files storing on FAT32.
Oh, and try to format your card with SDFormatter (google it) - 1024Kb allocation size, then partition in CWM.
pavlo_js said:
Did you flash v2.1 with fresh install? (Task29 etc.)
Check my installation here (I have no issues).
Click to expand...
Click to collapse
i am only having issues with point 3. ie. app solo performs slowly as compared to using v1.6 of this rom. and videos of (high) same bitrate now play slower. have you tested a high bitrate video that played on v1.6 and compared it to how it plays on v2.0 or v2.1 since HWA? or noticed sound processing delays when using apps like solo?
also you flash the adreno drivers. why? arent they included in the rom? if you did still with no issues, what was your method?
pavlo_js said:
Could you tell us a parameters of your memory card? We also have seen that one HD2 can behave different than another
Click to expand...
Click to collapse
its 16gb, i dont know what class it is. it came with the phone. i got this phone from a friend unopened a few months ago. but please remember, the problems i report in point 3. did not exist using the same card when using v1.6 rom.
pavlo_js said:
NexusHD2 is not using SWAP partition, so creating it has no point.
Click to expand...
Click to collapse
its been a while since i compiled a kernel, but if it is a flag that needs to be switched in the build, i cant see it taking up that much extra space in the image. is there any reason why there is no support for swap? again i still do not understand the manner in how this rom uses /dev/block/mtdblock5 swap/cache or if there is any benefit to using a swap partition that will ultimately reside on the sd card anyway (which is why im guessing there is swap as file within /dev/block/mtdblock5) but i have seen other roms mention support for swap.
pavlo_js said:
Maybe you should use a smaller partition size if you have enough space. I used 512MB and i still have 200MB free after install all my apps. Rest of files storing on FAT32.
Oh, and try to format your card with SDFormatter (google it) - 1024Kb allocation size, then partition in CWM.
Click to expand...
Click to collapse
you used a 512MB system partition? i guess you have the 1gig t-mobile. i have the 9193 telstra half gig phone; as i said recently, i am now using the minimal 165mb system partition; or do you mean some other partition, and why smaller?
anserinae said:
have you tested a high bitrate video that played on v1.6 and compared it to how it plays on v2.0 or v2.1 since HWA? or noticed sound processing delays when using apps like solo?
Click to expand...
Click to collapse
Unfortunately I have no comparison with v1.6 because I`m using NexusHD2 ICS since v2.0. I didn`t notice any delays in playback.
anserinae said:
also you flash the adreno drivers. why? arent they included in the rom?
Click to expand...
Click to collapse
From what I know, drivers were released several days later than the ROM
anserinae said:
but please remember, the problems i report in point 3. did not exist using the same card when using v1.6 rom.
Click to expand...
Click to collapse
So that is strange. It must be something deeper.
anserinae said:
you used a 512MB system partition? i guess you have the 1gig t-mobile.
Click to expand...
Click to collapse
I`m sorry. It's just a misunderstanding. I have HD2 EU. I meant 512MB EXT4 partition on SD Card. But now I don`t know if this has anything to do with your problem...
Maybe someone else will find a solution for your problem. I will try to think more about it.
pavlo_js said:
Unfortunately I have no comparison with v1.6 because I`m using NexusHD2 ICS since v2.0. I didn`t notice any delays in playback.
Click to expand...
Click to collapse
well the only way to compare high bite rate videos is to install the older rom. not that i think thats worth the effort. have you tried the (guitar) Solo app? and noticed that it lags behind after a few strums?
pavlo_js said:
From what I know, drivers were released several days later than the ROM
Click to expand...
Click to collapse
how did you do this?
pavlo_js said:
Maybe someone else will find a solution for your problem. I will try to think more about it.
Click to expand...
Click to collapse
well i guess i dont think i have any major problems. problems 1 & 2 are solved. no longer being able to use the musical apps because of sound processing issues is annoying but not the end of the world; i have seen a few posts in the official thread about sound issues, nothing as specific with any real case example like ive posted here however.
maybe if i get the chance to try the adreno drivers and flash the new kernel i can report back. i just havent made time nor jumped into doing so because they dont make mention of addressing any sound issues. *fingers crossed*
most of the videos i have play fine, i kept a few high bitrate videos on the card for testing purposes between rom versions which is why i mentioned it. i only started at rom v1.5. since moving to v2.0 some that used to play fine obviously no longer do so.
thanks alot for your feedback and help anyway mate
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.