Related
Since we had such an excellent turn-out in the ideas for lag-on-wake thread, resulting in a team effort to get the kernel bug identified and fixed, I figured we could do the same for the SD Card issues in the Viewsonic source code that result in some apps disappearing or being unable to install unless you unmount the internal SD card area before installation.
Rothnic does have a request into Viewsonic, since they seem to have addressed this issue between their two kernel builds but they neglected to release the patch for it.
But... that could take several days or several weeks to trickle through the bureaucratic food chain. I suspect this is a small change if we can isolate the area.
What I tried so far:
Just the dumb-obvious. There are three mmc drivers directories in the VS patch, mmc, mmc_orig, and mmc-new. The only one getting built is the mmc directory. I diffed the mmc and mmc-new files, and tried building the mmc-new driver instead, but didn't observe any difference in behavior with respect to the mounting issues (i.e. error -18 when I try to install Angry Birds from market). The diff between these driver file sets is quite small, and limited to a few files.
What I suspect:
There is an "install to SD card" option built-in to some apps. I suspect that the apps affected by this may be the ones that enable this option. Perhaps something to do with the loopback device Android tries to create on the SD card for external app storage (http://android-developers.blogspot.com/2010/07/apps-on-sd-card-details.html)?
Why this relates to the kernel:
Well, the issue doesn't occur with the latest kernel build from Tap N Tap and does with our kernels. There are user-space workarounds (unmounting SD card) and some of that may be workable into our ROMs, but I'd like to get a kernel that is a drop-in replacement for the stock kernels.
Consider the following patch which just enables some "stuff" in the kernel.
http://nv-tegra.nvidia.com/gitweb/?...it;h=555d0c0e5b9a86b5e291216d59406709b34480d6
For me clicking on the link you included yields a page not found...
rcgabriel said:
Since we had such an excellent turn-out in the ideas for lag-on-wake thread, resulting in a team effort to get the kernel bug identified and fixed, I figured we could do the same for the SD Card issues in the Viewsonic source code that result in some apps disappearing or being unable to install unless you unmount the internal SD card area before installation.
There is an "install to SD card" option built-in to some apps. I suspect that the apps affected by this may be the ones that enable this option. Perhaps something to do with the loopback device Android tries to create on the SD card for external app storage (http://android-developers.blogspot.com/2010/07/apps-on-sd-card-details.html)?
Click to expand...
Click to collapse
rcgabriel said:
some apps disappearing or being unable to install unless you unmount the internal SD card area before installation.
Click to expand...
Click to collapse
Is it possible to unmount the internal SD card area while running the OS? I've used the mount / unmount options in CWM, but have not found a way to unmount /sdcard inside the OS. Wouldn't this be like cutting off the branch you are standing on? I'm currently running TnT Lite 3.1.2. Thanks.
Just a thought, but how does a standard android system's mounting structure run? Isn't it something to the tune of some other root folder than /sdcard, and when an sdcard is inserted that gets mounted to /sdcard? Is there a reason we don't have our roms mounting in this way, and would this not improve compatibility with the android system and apps as a whole?
If the issue is that people would then have to have an sdcard for a lot of things, perhaps we put those to /sdcard2 and partition a gig or two slice of the internal storage to mount at /sdcard so the internal storage can abide both concerns..
Am I way off in just thinking the systems mounting structure might be better served to mirror a standard android system? Does it already and I'm just being dingy?
vsc said:
Consider the following patch which just enables some "stuff" in the kernel.
http://nv-tegra.nvidia.com/gitweb/?...it;h=555d0c0e5b9a86b5e291216d59406709b34480d6
For me clicking on the link you included yields a page not found...
Click to expand...
Click to collapse
Fixed that link, but yeah, that looks like a very promising patch, and it's just config file changes....
The question is whether the CONFIG_BLK_DEV and CONFIG_BLK_DEV_LOOP stuff is also dependent on other patches to the mmc driver or other kernel files.....
EDIT: I cherrypicked the relevant-seeming config file changed from that patch, rebuilt the kernel, and am testing it.
BINGO! Angry birds installs again without having to remount. More coming...
See config_patch attached for the specific changes I made. For kernel devs, just unzip this into your arch/arm/configs dir and patch -p0 < config_patch.
I figured...
The thing that I don't know is why does TnTLite not have issues. But this can't hurt. Post your config so we are working with the same configuration and I'll give it a try with TnTLite.
rcgabriel said:
Fixed that link, but yeah, that looks like a very promising patch, and it's just config file changes....
The question is whether the CONFIG_BLK_DEV and CONFIG_BLK_DEV_LOOP stuff is also dependent on other patches to the mmc driver or other kernel files.....
EDIT: I cherrypicked the relevant-seeming config file changed from that patch, rebuilt the kernel, and am testing it.
BINGO! Angry birds installs again without having to remount. More coming...
Click to expand...
Click to collapse
vsc said:
I figured...
The thing that I don't know is why does TnTLite not have issues. But this can't hurt. Post your config so we are working with the same configuration and I'll give it a try with TnTLite.
Click to expand...
Click to collapse
Config uploaded above. I included the crypto stuff because I believe the loopback block device that Android uses requires it, but everything may work without it. Not certain.
I think the crypto stuff is required.
rcgabriel said:
Config uploaded above. I included the crypto stuff because I believe the loopback block device that Android uses requires it, but everything may work without it. Not certain.
Click to expand...
Click to collapse
Very nice find guys.
Have now integrated this into my kernels posted in the lag-on-wake issue thread.
v12xke said:
Is it possible to unmount the internal SD card area while running the OS? I've used the mount / unmount options in CWM, but have not found a way to unmount /sdcard inside the OS. Wouldn't this be like cutting off the branch you are standing on? I'm currently running TnT Lite 3.1.2. Thanks.
Click to expand...
Click to collapse
I Have the same question...I dont run cwm
Posted an update for TnTLine on the other thread as well. My problem is when I reinstall AB and run it I have to force myself to get out of the game....
rcgabriel said:
Have now integrated this into my kernels posted in the lag-on-wake issue thread.
Click to expand...
Click to collapse
I think enabling twofish under crypto would fix this. Will build one later when I get home: )
Update:
I basically enabled two fish and others..The most important thing was to install Devmapper and Dev Crypt in the kernel to get it up and running..Consider this issue SOLVED.
OK got Angry Birds installed without unmounting SD. Will continue testing..Everything seems to be fine..I'm uploading..Please test...Just put clempatch.zip in your internal SD and install.
vsc said:
Posted an update for TnTLine on the other thread as well. My problem is when I reinstall AB and run it I have to force myself to get out of the game....
Click to expand...
Click to collapse
Try my fix above
Here's an idea.
We use additional EXT partition on our SD cards to extend memory of 512MB Leos.
Why not turning it into a RAID matrix?
I use software RAID on my desktop Linux, why not here?
I'm not sure if its even possible.
It also might actually slow down the devices because of the differences between both memories, but it's worth a try, isn't it?
Any one skilled and willed enough to do this?
tomus said:
Here's an idea.
We use additional EXT partition on our SD cards to extend memory of 512MB Leos.
Why not turning it into a RAID matrix?
I use software RAID on my desktop Linux, why not here?
I'm not sure if its even possible.
It also might actually slow down the devices because of the differences between both memories, but it's worth a try, isn't it?
Any one skilled and willed enough to do this?
Click to expand...
Click to collapse
Well, RAID0 would require both volumes to be the same size, or it will cap it to the size of the smallest one. So the best you could get would be 1024 for EU, 2048 for US.
So, how about you start begging Cotulla for the MAGLDR source (or find some way to implement it into Android) and dedicate the next two years to it Nothing is impossible, but it definitely isnt plausible.
I'm not sure what are the differences between the desktop Linux kernel and the Android one (I actually think they are the same with some addons, can anyone clarify on that?), but there is support for software RAID in the Linux kernel. We could create a system partition in NAND, another one of the same size on SD and "software-RAID them up" Whole matrix is being assembled during init, so no need for any low level code.
I guess we would need some initrd, or non-RAID boot partition with kernel...
It would also require to build matrix and filesystem on the device (instead of flashing already pre-created one) or flashing both NAND memory and RAID partition on the SD card...
Also software RAID impacts the CPU performance on IO. I'm very curious how it would run
Talking about desktop kernel... Maybe I should try in the Ubuntu section? ;P
tomus said:
I'm not sure what are the differences between the desktop Linux kernel and the Android one (I actually think they are the same with some addons, can anyone clarify on that?), but there is support for software RAID in the Linux kernel. We could create a system partition in NAND, another one of the same size on SD and "software-RAID them up" Whole matrix is being assembled during init, so no need for any low level code.
I guess we would need some initrd, or non-RAID boot partition with kernel...
It would also require to build matrix and filesystem on the device (instead of flashing already pre-created one) or flashing both NAND memory and RAID partition on the SD card...
Also software RAID impacts the CPU performance on IO. I'm very curious how it would run
Talking about desktop kernel... Maybe I should try in the Ubuntu section? ;P
Click to expand...
Click to collapse
A RAID Partitioning would be great if we would use it like WP7 (which i have tested for a week), its working great but if i remember what wp7 does, if you remember the sdcard (you MUST reflash Wp7 to get everything to work again) it would be less attractive than before.... :/
Sounds like you want JBOD (which isn't really raid, but related, and usually implemented in the raid tools), and it's not required to have same size disks. If it's possible to implement, you could then add on a 32g SD card onto the built-in NAND to create a 33g virtual NAND(TMOUS).
http://en.wikipedia.org/wiki/Non-RAID_drive_architectures
OK, so let me first apologise for being new to this and completely dumb. I am currently using an iphone and looking to move over to a SGN. I am pretty competent with computers, phones etc, and jailbreaking iPhone. I have messed with Linux in my spare time, so I am not afraid of detailed technical work. I have also done dozens of hours of research on how to hack android phones. The basic issue I have is that I haven’t found a single guide that explains it all clearly in one place, and also exploits are getting patched and being outdated (Zergrush for example)
I am reasonably comfortable with the threads on how to root, install CWM, and the different ROM’s explain how to install them, or at least there are multiple ways to attempt these things. It is a bit confusing because there is different advice on using or not using Odin, Mobile Odin, Kies etc, and their effect on the binary counter.
I have a few questions though, and I thought posting here might get some responses:
1). I would like to change the partition size for apps stored on the internal SD card. I have watched lots of youtube videos on this, and people suggest it can be done with ROM, CWM, Odin, and also directly on a PC with partition magic. What I don’t get is the partition structure within the phone. If this is done won’t it wipe the space where CWM and the recovery console is stored and brick the phone? Could someone explain what the partition structure is, and the best way to manage partition sizes. I believe that the SGN come with 1.8gig size for apps, and the rest for storage of music, pictures etc. I would rather have a much bigger size for apps internally, and keep music and pictures on the external SD card. I have seen the use of apps like Link2SD, Move2SD etc, but I want to sort out the partition sizes first.
2). Could someone also please explain what occasion might cause you to upgrade the Kernal. My assumption would be that everyone would want to be running the latest kernel, but it seems that people are running different kernals. Is this because they are closely tied with the ROM/firmware, and they are upgraded when the custom ROM is installed, so some suit different ROMS?
3). I would welcome any link to a page that explains all of the topics in order and really clearly e.g How to Root, then install CWM, then partition. Whether to use Odin, Mobile Odin, Kies etc.
You advice would be appreciated.
chriswilson_m3 said:
OK, so let me first apologise for being new to this and completely dumb. I am currently using an iphone and looking to move over to a SGN. I am pretty competent with computers, phones etc, and jailbreaking iPhone. I have messed with Linux in my spare time, so I am not afraid of detailed technical work. I have also done dozens of hours of research on how to hack android phones. The basic issue I have is that I haven’t found a single guide that explains it all clearly in one place, and also exploits are getting patched and being outdated (Zergrush for example)
I am reasonably comfortable with the threads on how to root, install CWM, and the different ROM’s explain how to install them, or at least there are multiple ways to attempt these things. It is a bit confusing because there is different advice on using or not using Odin, Mobile Odin, Kies etc, and their effect on the binary counter.
I have a few questions though, and I thought posting here might get some responses:
1). I would like to change the partition size for apps stored on the internal SD card. I have watched lots of youtube videos on this, and people suggest it can be done with ROM, CWM, Odin, and also directly on a PC with partition magic. What I don’t get is the partition structure within the phone. If this is done won’t it wipe the space where CWM and the recovery console is stored and brick the phone? Could someone explain what the partition structure is, and the best way to manage partition sizes. I believe that the SGN come with 1.8gig size for apps, and the rest for storage of music, pictures etc. I would rather have a much bigger size for apps internally, and keep music and pictures on the external SD card. I have seen the use of apps like Link2SD, Move2SD etc, but I want to sort out the partition sizes first.
2). Could someone also please explain what occasion might cause you to upgrade the Kernal. My assumption would be that everyone would want to be running the latest kernel, but it seems that people are running different kernals. Is this because they are closely tied with the ROM/firmware, and they are upgraded when the custom ROM is installed, so some suit different ROMS?
3). I would welcome any link to a page that explains all of the topics in order and really clearly e.g How to Root, then install CWM, then partition. Whether to use Odin, Mobile Odin, Kies etc.
You advice would be appreciated.
Click to expand...
Click to collapse
The time it took you to write this thread is almost the same as searching on xda for finding most of your answers
1. Partition is set with pit file, which is available with ROM, when you flash ROM with Odin, there you may see the option to re-partition, though you dont have choice to select the size manually on odin, you have to select the .pit (partition index table)file, which design the partition. As I know it comes default, some one make it manually i dont know. BUT listen carefully it is not without risk to brick phone, and thats why pit file in normal case you can't see in ROM package.
2. Most of near ROM kernel are alike. e.g. I M on LA4, safely using kernel KL7. ROM package it self contains kernel, so when you update it, it gets updated too. BUT in case of getting CWM you may need to select near kernel when exact kernel not available. More when you flash your ROM with CWM, you will given option to keep old kernel (to keep Root intact)
3. most of question regarding ROM , Installation , Rooting you will find on links on my signature.
Thanks Dr Ketan for your detailed response. I have actually read and bookmarked many of your threads as there are very informative and detailed.
I understand your response about the ROM and the Kernal, and also the PIT file setting the size of the partitions.
I guess then if you want to change the partition size of the internal memory, then that is something that is not normally done. It seems that most people partition the external SD card, and use link2SD to utilise the space as part of the extended memory. Would you say that is the best approach?
I can say it is safest way.
why do you feel the need to try to repartition?
1gb rom size is sufficent for any rom
2gb internal data is more than sufficient unless you like to install 100's of apps
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.