Related
Will all Eclair roms require Death SPL from now on? Or will it be possible to make a rom for those of us running stock?
I doubt that would be possible with those tmobile apps added in and ringtones and boot screen and multitouch screens with bluray players.
So maybe cause untrustful sites said it was in the works. But dont worry about MT3G they will have it and a MT3G fender and V2 will be out this year w/ 2.1 update.
Ace42 said:
I doubt that would be possible with those tmobile apps added in and ringtones and boot screen and multitouch screens with bluray players.
So maybe cause untrustful sites said it was in the works. But dont worry about MT3G they will have it and a MT3G fender and V2 will be out this year w/ 2.1 update.
Click to expand...
Click to collapse
No I meant custom roms for those with root on stock spl. The ringtones don't have to be added to the rom zip file, they can be a separate zip and added to the sdcard like cyanogen does with his rom. My g1 refuses to flash radio updates for some reason so I can't update to haykuros spl.
I'm thinking about porting Manup or JAC's Eclair to fit stock SPL as well. Moving apps to /data and using minimal Audio.
smackdown85146 said:
I'm thinking about porting Manup or JAC's Eclair to fit stock SPL as well. Moving apps to /data and using minimal Audio.
Click to expand...
Click to collapse
That would be extremely awesome! If I knew more about rom development id have done the same. I'm guessing its not as easy as deleting/moving the ringtones to a separate zip and moving apps to /data, and resigning the zip? Is there more to it than that when porting to stock spl?
speedysilwady said:
That would be extremely awesome! If I knew more about rom development id have done the same. I'm guessing its not as easy as deleting/moving the ringtones to a separate zip and moving apps to /data, and resigning the zip? Is there more to it than that when porting to stock spl?
Click to expand...
Click to collapse
Probably, but I'm still a noob at developing so I'm still trying to get the hang of this.
smackdown85146 said:
Probably, but I'm still a noob at developing so I'm still trying to get the hang of this.
Click to expand...
Click to collapse
Either way it'd be great if you got it to work. Plus it'll help you hone your skills. I believe that might be all that's required to get it to work, but the problem is knowing which apps to move to data and which ones to keep in system. I think cyans wiki mentions "barebones" apps that can or can't be deleted from system or data because they may or may not be required by android to run properly. it'd be nice to see what you and the community can come up with!
To me, manup456's rom looks like it will work on a stock SPL. He already has the /system/app moved over to /data/app_s and symlinked back. I *believe* that despite the claim in the first post, that it in fact does NOT require the deathspl.
lbcoder said:
To me, manup456's rom looks like it will work on a stock SPL. He already has the /system/app moved over to /data/app_s and symlinked back. I *believe* that despite the claim in the first post, that it in fact does NOT require the deathspl.
Click to expand...
Click to collapse
did u test those roms...i couldnt find any roms that would work with Hard SPL
geokuttan said:
did u test those roms...i couldnt find any roms that would work with Hard SPL
Click to expand...
Click to collapse
I said manup456's.
Take a look at it, it only uses 62.4 MB in /system. The original size of /system is 67.5 MB. 39.5 MB of 74.8 in /data for system apps, but with apps2sd that is fine.
Personally, I would put the extra 40 MB into /cache instead of /data, this way apps2sd won't be strictly required, but it'll work either way.
Note the ONLY difference between the deathSPL and engineering SPL, aside from the brickrisk associated with deathSPL, is the partition layout. Since it'll fit, it'll work.
lbcoder said:
I said manup456's.
Take a look at it, it only uses 62.4 MB in /system. The original size of /system is 67.5 MB. 39.5 MB of 74.8 in /data for system apps, but with apps2sd that is fine.
Personally, I would put the extra 40 MB into /cache instead of /data, this way apps2sd won't be strictly required, but it'll work either way.
Note the ONLY difference between the deathSPL and engineering SPL, aside from the brickrisk associated with deathSPL, is the partition layout. Since it'll fit, it'll work.
Click to expand...
Click to collapse
yea manup456's Eclair2.1 Rom doesnt work with hard SPL v1.5
Error:
E: Failure at line 344:
installation aborted
geokuttan said:
yea manup456's Eclair2.1 Rom doesnt work with hard SPL v1.5
Error:
E: Failure at line 344:
installation aborted
Click to expand...
Click to collapse
Sure it does.
Did you bother reading the update-script at line 344 to understand your error?
Line 344: copy_dir PACKAGE:data DATA:
Very few things can make this fail;
1) /data partition is full,
2) /data doesn't exist within the update archive,
3) /data partition is corrupt.
If you observe the preceding lines in the script, he does NOT FORMAT the /data partition. He clears /data/app, /data/init.rc, /data/local, and /data/dalvik-cache. /data has other stuff, like /data/system, /data/data, etc., and these take up space. Even after clearing those things, YOURS obviously still doesn't have at least 39.5 MB available. So I suggest that you WIPE your /data partition before trying to install this.
Another little note about this particular image: **after** installing it, DO NOT WIPE YOUR /data PARTITION!!! If you do, you will delete all the system apps!
One other minor possible glitch to be aware of... once the system starts creating dalvik-cache files, it is possible that the /data partition will overfill. If this happens, you might want to move some crap from /data into /cache.
lbcoder said:
Sure it does.
Did you bother reading the update-script at line 344 to understand your error?
Line 344: copy_dir PACKAGE:data DATA:
Very few things can make this fail;
1) /data partition is full,
2) /data doesn't exist within the update archive,
3) /data partition is corrupt.
If you observe the preceding lines in the script, he does NOT FORMAT the /data partition. He clears /data/app, /data/init.rc, /data/local, and /data/dalvik-cache. /data has other stuff, like /data/system, /data/data, etc., and these take up space. Even after clearing those things, YOURS obviously still doesn't have at least 39.5 MB available. So I suggest that you WIPE your /data partition before trying to install this.
Another little note about this particular image: **after** installing it, DO NOT WIPE YOUR /data PARTITION!!! If you do, you will delete all the system apps!
One other minor possible glitch to be aware of... once the system starts creating dalvik-cache files, it is possible that the /data partition will overfill. If this happens, you might want to move some crap from /data into /cache.
Click to expand...
Click to collapse
i did a wipe before installing this rom...i have like 50 mb free space available...
i am planning on updating to ENG SPL....but lot of people said its really risky...
geokuttan said:
i did a wipe before installing this rom...i have like 50 mb free space available...
i am planning on updating to ENG SPL....but lot of people said its really risky...
Click to expand...
Click to collapse
Wrong, it is really risky going to the Haykuro spl (Also known as the Death or Danger spl). While flashing anything is risky, the spl your going to flash isn't really risky when compared to the Haykuro spl.
JAguirre1231 said:
Wrong, it is really risky going to the Haykuro spl (Also known as the Death or Danger spl). While flashing anything is risky, the spl your going to flash isn't really risky when compared to the Haykuro spl.
Click to expand...
Click to collapse
someone said that Haykuro roms iwll probably work with Eng SPL...
The haykuro spl is not hard to flash. There was a lot of confusion when it first came out, but it really is nothing to worry about. Check the link to my Nex^2us theme, there are instructions on flashing the spl that have worked well for everyone (so far).
cloverdale said:
The haykuro spl is not hard to flash. There was a lot of confusion when it first came out, but it really is nothing to worry about. Check the link to my Nex^2us theme, there are instructions on flashing the spl that have worked well for everyone (so far).
Click to expand...
Click to collapse
I was kinda confused cuz...i already have RADIO-2.22.19.261(If i flash the radio again will it brick my phone?)....so do i still need to flash the radio again and then flash the haykuro spl you have? also i will not loose anything right...like i have Amon Ra recovery and switchrom with a few roms....
geokuttan said:
I was kinda confused cuz...i already have RADIO-2.22.19.261(If i flash the radio again will it brick my phone?)....so do i still need to flash the radio again and then flash the haykuro spl you have? also i will not loose anything right...like i have Amon Ra recovery and switchrom with a few roms....
Click to expand...
Click to collapse
Even if you are certain you have the correct Radio, you flash the radio anyway, as it will prevent a brick. The purpose of this is many people "know" they have the correct radio, then flash the spl and brick, because they in fact did not have it.
You will not lose your recovery. Other than an increase in space, you will not notice anything.
cloverdale said:
Even if you are certain you have the correct Radio, you flash the radio anyway, as it will prevent a brick. The purpose of this is many people "know" they have the correct radio, then flash the spl and brick, because they in fact did not have it.
You will not lose your recovery. Other than an increase in space, you will not notice anything.
Click to expand...
Click to collapse
Other than the loss of a rom...
cloverdale said:
The haykuro spl is not hard to flash. There was a lot of confusion when it first came out, but it really is nothing to worry about. Check the link to my Nex^2us theme, there are instructions on flashing the spl that have worked well for everyone (so far).
Click to expand...
Click to collapse
I have one more question ..in the 6th step you said that i need to flash the HTC recovery...i already have Amon ra so after i flash the SPL i can just restore a rom using switchrom right...
JAguirre1231 said:
Other than the loss of a rom...
Click to expand...
Click to collapse
well i have backed up my roms using Amon Ra switchrom...its in the sd card so it will be safe...
what is the largest rom that i can flash to my g1 with danger spl?
Any rom taht uses the (death,danger,haykuro) SPL can be flashed devs try to make it fit with out danger, but sometimes its jus needed for all the extras
yerand said:
what is the largest rom that i can flash to my g1 with danger spl?
Click to expand...
Click to collapse
DeathSPL makes no difference regarding the maximum size of ROM you can flash since we can now load custom partition tables with ANY SPL. The maximum size that you can store INTERNALLY is about 208 MB (would require userdata and cache on the sdcard though.
Technically, anything less than or equal to 208 can be stored internally, though theoretically, you could store part of a ROM on the SDCARD, which is up to 32 GB, so 32GB+208MB - a little bit of space for userdata+cache. If you want everything internal, then it is up to you to figure out how you want your storage allocated.
Hello Everyone
I rooted and already have my phone the way I want it but I've noticed that when you do the full wipe
theres like 7 gigs of space missing. I was wondering if anyone was able to at least get most of their space back when they wipe the phone
if so how can i do it?
I currently running the Rage Rom thinking of going back to Ecliptic ONE
and i have TWRP recovery
any ideas will be appretiated thanks
Have you made any backups?
g00s3y said:
Have you made any backups?
Click to expand...
Click to collapse
I made a back up but i deleted it unless theres another back up am missing somewhere?
how much space you supposed to have after the full wipe?
I recently did a full wipe and it was like 6.x gigs right off the bat. It boggles the mind, considering there are phones out there that have only that much total capacity.
Wtf htc.
Does anyone know how much space AOSP roms take? I'm switching once the installer comes out.
sauprankul said:
I recently did a full wipe and it was like 6.x gigs right off the bat. It boggles the mind, considering there are phones out there that have only that much total capacity.
Wtf htc.
Does anyone know how much space AOSP roms take? I'm switching once the installer comes out.
Click to expand...
Click to collapse
AOSP ROMs are typically around 120-150 Megs zipped, sense ROM go.from 700 to a little over 900 MB's zipped.
https://vzwsupport.jive-mobile.com/#jive-discussion?content=/api/core/v2/discussions/804286
It's only 25 GB available left. :-[
Sent from my m7spr using tapatalk4
phatmanxxl said:
AOSP ROMs are typically around 120-150 Megs zipped, sense ROM go.from 700 to a little over 900 MB's zipped.
Click to expand...
Click to collapse
Right, but I'm asking for how much CM takes after installation and clean wipe. I'm not sure how compression works, so this may be wrong, but if I set up a proportion (I'm almost sure you can't do that), CM comes to 1.5 gigs installed (205meg for 10.2 zipped), which seems more reasonable.
It really sucks that I have to keep clearing out stuff because I start with only like 25 gigs of space rather than 31.5.
Can somebody who has 10.2 installed comment?
if its off a fresh boot, it's because of all the apps that prolly installed to the internal sd got erased, thats why you had more space, and still have your files and stuff
ticklemepinks said:
if its off a fresh boot, it's because of all the apps that prolly installed to the internal sd got erased, thats why you had more space, and still have your files and stuff
Click to expand...
Click to collapse
I (tried to) delete ALL data from my phone and it was still 7 gigs.
Got this explanation from another site.
The 32GB are in 1000Byte = 1KB Logic, and the 25GB should be in Binary Logic, so 1024Byte = 1KB. which gives at first a "loss" of about 2GB: 32GB = 29,8023GiB
the rest of the space is mostly the android system, reserved space for cache etc... one small part will be the journal of the ext file sytstem which is used instead of yaffs. So arround 200-400MB i think will be covered by the ext journal.
you have the same problem with harddisks too. The firms write it in decimal logic but the operating system does it in binary. Some Operating Systems nowadays also write the correct GiB or MiB or KiB but not all...[\quote]
Click to expand...
Click to collapse
use a file explorer and go back as far as you can. Check /data/media. if you've ever flashed a 4.2 rom it moves all your files around and it gets confusing.
If that doesn't find it, download Diskusage. it could help you out.
Hello,
as I see there are some kernels and roms, but for me key question is how much internal memory can I gain after removing write protection (I couldn't find such information).
I know that it probably depends on how much I decide to delete, but I would be thankful if someone wrote:
- which applications take most of the space?
- what is "other" in memory management that takes almost 3GB?
Then I will know if rooting etc. is worth the trouble and warranty loss risk.
Thank you in advance.
Regards,
Chris
3 GB "Other" is the ROM of the phone, you basically have about 1 GB to use. You need a custom ROM to have more space, since in most of the custom ROMs the bloatware, the htc sence, htc keyboard etc are all deleted which frees up some space, but don't expect a lot.
nekubg said:
3 GB "Other" is the ROM of the phone, you basically have about 1 GB to use. You need a custom ROM to have more space, since in most of the custom ROMs the bloatware, the htc sence, htc keyboard etc are all deleted which frees up some space, but don't expect a lot.
Click to expand...
Click to collapse
Custom rom not help. Partition and data system has a fixed size. Deleting bloatware free up space on the system partition. Which is unusable.
Then its worse than I thought...
ufonek said:
Custom rom not help. Partition and data system has a fixed size. Deleting bloatware free up space on the system partition. Which is unusable.
Click to expand...
Click to collapse
Wow, so it seems that in terms of free space rooting this phone gives you nothing. And that was my main motivation.
Is it possible to change partition size after freeing space? I mean some kind of gparted-thing.
Regards,
Chris
strangeFace said:
Wow, so it seems that in terms of free space rooting this phone gives you nothing. And that was my main motivation.
Is it possible to change partition size after freeing space? I mean some kind of gparted-thing.
Regards,
Chris
Click to expand...
Click to collapse
Well, at least not something im willing to try, because the chances are to big that I brick my phone.
AFAIK, the partition table (partition size, place etc.) are stored in your hboot. Flashing a custom hboot is possible with S-OFF, but I don't know what I should edit in hboot to change the partition size., and I'm not really willing to try it.
factory reset does not help
Hi guys,
I made factory reset, but the "other" folder is still 2,88 GB out of 4 available after reboot. There are no pictures, videos, games or apps whatsoever, its fatory clean!!, and I don't know what this 2,88 GB data is?
I have a suspect on the /sys folder, which contains more than 500 thousands files! with folder like loop, mmcd...etc. see via ES file explorer. also not thumbnail found.
Any idea how to get rid of that data?
thanks.
ciao,
Rob.
Taken from CM12 thread as this started to become off-topic. The issue I'm trying to address is how to stuff a huge Lollipop ROM directly into internal storage, without creating a virtual slot, to increase system performance and have overall cleaner solution. Original inspiration: @Mentor.37's custom Safestrap for unused partitions, which has way too small /data for me unfortunately. (explanation)
sd_shadow said:
Septfox said:
This in mind, is there any way to repartition the internal (stock) storage to decrease the size of /cache/ and create a larger /data/ partition, or is it not possible without modifying the bootloader?
Click to expand...
Click to collapse
Code for mounting the unused preinstall and webtop partitions to SD storage http://forum.xda-developers.com/showthread.php?p=59253593
Click to expand...
Click to collapse
This allows you to mount the partitions either as a new storage or to a specific directory only, in other words it does not merge the storages, just adds a mount point next to (or possibly if modified a bit on the top of) other storage. While this may be useful for taking some inherent load off /storage/sdcard0/ (i.e. mounting /dev/block/webtop to /storage/sdcard0/Downloads) for people not swapping their sdcards, it doesn't help in Septfox's intention of enlarging /data/.
I face the same problem as Septfox: I'd love to use the storage intended for running system for it, not virtually mounted storages created in the storage intended for storing media and support data. However, the outline of the storage is intended for way older and less robust system so even the /system/ is not quite enough (667 MB, which tightly fits CM12 with a small GApps package) and /data/ is also not enough for heavier use (3.22 GB). Therefore I would like to merge it with currently unused partitions: maybe join preinstall to system and webtop to data, making both big enough.
One alternative would be to mount the 1.4 GB webtop as /data/app, which currently makes about 2/5 of occupied space of my /data. Is this possible? At which point of system startup is the script in /system/etc/init.d executed (is it done by Safestrap or the ROM itself?), and at which point might the system first need to access /data/app that contains the APKs of user-installed apps? All the really needed stuff (compiled executables) is in the /data/dalvik-cache, right? Here I'm on a really thin ice, don't know much about Android's architecture, so sorry if this is a major bullsh*t - just throwing my idea in Technically what I'm talking about is such modification of the script:
Code:
#!/system/bin/sh
mount -o rw,remount /data # Not too sure about this
# - depending on whether /data is already rw or not.
# For that I would need to know when is the script
# executed. I'm almost sure this is not necessary
# though. In original script this was done to allow
# writing into /storage/.
mkdir /data/app
#mount -o ro,remount / - unnecessary, see above
#mount -t ext3 /dev/block/preinstall /storage/preinstall
# I don't see any use for small preinstall partition.
mount -t ext4 /dev/block/webtop /data/app
chmod 777 /data/app # not sure about this either,
# probably should be 771
Clean version:
Code:
#!/system/bin/sh
mount -o rw,remount /data # Unnecessary?
mkdir /data/app
mount -t ext4 /dev/block/webtop /data/app
chmod 777 /data/app # Possibly 771 instead.
Is that possible to run, or will it bootloop, what do you think?
Even better IMO would be to delete preinstall and webtop and shrink the Stock data down to maybe 200 MB so the original Stock system is still present, preventing the phone from bricking and accommodating Safestrap. The remaining space could be divided between Safe system (say 800 MB) and Safe data (over 4 GB). Are we able to do this somehow, maybe by customizing Safestrap a bit more? Or are partitions in /dev/block locked by bootloader? Also are all these and Internal storage located on the same physical chip, or are there two separate memories in the D4? Attached proposal of repartitioned layout Sizes taken from here and here.
Developers and experienced users, I would love to hear your opinion, mainly on whether repartitioning internal storage or at least mounting webtop to /data/app could work on D4. Thanks!
Addition to the original post:
I have a spare D4 with shattered screen and not working SIM slot that I bought for spare parts. Apart from GSM (or telephony altogether? I didn't try, as only option would be emergency call which I don't want to abuse, and we don't have CDMA networks here) it works fine though. I can try meddling with formatting/partitioning - it won't be too big deal if it gets bricked beyond possibility of SBF restore.
Replies so far, taken from the original CM12 thread:
sd_shadow said:
I don't think repartitioning is possible without high risk of hard bricking the device, and yes the locked bootloader does limit what can be done.
This is quite off topic, and you should start a new thread if you are going to continue.
Click to expand...
Click to collapse
Good call, started new thread
lucize said:
tried to change the type of preinstall partition and the device would boot into fastboot: (invalid cg hab (cg: ebr, status: 0x0056)
so a recovery is needed, I'll try a resize if I can compile the tools in safestrap. but I think it would not work
later edit: used fdisk to resize in safestrap and it broke again so it can't be done
Click to expand...
Click to collapse
Thanks for trying! What do you mean by changing type?
As I added here in the first post, I have a spare shattered but mostly working D4 I wouldn't be too sad to see bricked - I can try out more dangerous stuff if you point me in the right direction. I'd like to help testing different approaches to repartitioning if you have some potentially harmful ideas that you wouldn't try on your own phone.
Curious question aside: where is bootloader (and fastboot) stored? Is it sitting on some other small partition? Can we mount it to be read, or even to write there? What/where is that protection that keeps us from unlocking the bootloader?
Also, concerning mounting the free partitions to other system partitions: do you think it's possible to mount them as a folder in /data (whichever we use)? Does it matter what filesystem the partitions use? What part of boot-up runs the /system/etc/init.d/ scripts? Do you think attached proposals 2 or 3 are feasible? It would still have the stock system untouched for an emergency use and Safestrap storage, but its data would be shared with the safe system, with webtop mounted as /data/app or /data/data (1.4 GB should suffice I hope) which would leave us with nice 3.2 GB for the rest. Of course, preinstall's 600 MB for /system is hardly enough for CM12 with Pico version of PA GApps so the rest of used Google apps would inflate /data a bit - but still this is probably the best option we have now.
Actually, I find the stock /system/ to be adequate. Yea, it's a tight fit, but CM12+PA Micro Gapps slots in with 30-someodd megabytes to spare, and there shouldn't be any real need for additional space on top of that. Though, I suppose there could be trouble if CM starts including larger apps.
Init.d is done by the ROM itself, and has to be enabled at build time; CM12 actually has it shut off for whatever reason (Slimkat did as well, I would imagine CM11 also did). There's an app called "Universal Init.d" in the Store, but by the time it can get around to executing the scripts, it's obviously way too late to be screwing with vital partitions : \
Worth pointing out that Safestrap appears to have proper ADB access, you might be able to do something with partitions thataway. I don't know enough about partitions and mounting in Linux to take a jab at it. Woop, looks like that's already a no-go. Maybe the bootloader does a check or three to make sure the partitions are all in order, and throws a critical error if not.
If absolutely all else fails, there's still symlinking large apps into the newly-accessible partitions that can be done, either manually or with Link2SD/similar apps. It's a bit of a hassle, but an option nonetheless.
Well, stock /system is fine but I want to keep it untouched - mainly because I don't want to install CM12 as an update over stock JB, and also to keep myself from SBFing (at least in the long run) because of trivial issues. When this option is off the plate, the remaining partitions don't seem to offer enough space to run CM11 in a non-virtual slot (as Mentor.37 offers with his modified Safestrap with a "Safe" slot with 600M system and 1.4G for data).
Symlinking is an ugly solution - used it for a while, never liked it, mainly because symlinks broke once SD got unmounted or mounted as Mass Storage, with problems remounting afterwards.
Since we can modify the system freely, I'm sure that if necessary, we could make a neater solution than using an app to create symlinks after boot. Question how early in the boot process can we add some scripts (by flashing some zipped patch over the ROM) goes to more knowledgeable devs though...
first time I just used t option in fdisk to change partition type to whatever without changing size, the second time I resized some of them and every time after 1st reboot the M logo would appear for 1 second and from now on it would go straight into fastboot without M logo, so it seems that something in bootloader is verifying the layout or something and if is not good it would stop.
I don't think that it's possible to brick it for good, use rsd to recover
Regards
Thanks to @lucize for his trying, sadly it seems we can't repartition at all
@Mentor.37, is there a source to your customized SS 3.75 available? I'd like to try and mess around with it to put the Proposal 3 from my second post's attachment to work.
Could mounting and symlinking be done from Safestrap, or does the ROM do it itself? I have ideas of various cross-linking of folders on the partitions to kind of emulate repartitioning - but I'd have to try if it works and it would need to be done either before the system boot or shortly in the process. See attachment - that's a first draft I presume for this that the user keeps stock system only for keeping the phone bootable no matter what happens in other than stock slots, so stock data would be utilized only for root and safestrap, leaving most of its 3.2 GB free.
LuH said:
Thanks to @lucize for his trying, sadly it seems we can't repartition at all
@Mentor.37, is there a source to your customized SS 3.75 available? I'd like to try and mess around with it to put the Proposal 3 from my second post's attachment to work.
Could mounting and symlinking be done from Safestrap, or does the ROM do it itself? I have ideas of various cross-linking of folders on the partitions to kind of emulate repartitioning - but I'd have to try if it works and it would need to be done either before the system boot or shortly in the process. See attachment - that's a first draft I presume for this that the user keeps stock system only for keeping the phone bootable no matter what happens in other than stock slots, so stock data would be utilized only for root and safestrap, leaving most of its 3.2 GB free.
Click to expand...
Click to collapse
I believe that it's impossible because symlinking "works" after kernel is loaded and safetrap take place (is loaded) before a kernel is loaded....
If I'm not mistaken, symbolic linking is a filesystem thing, something like a shortcut only more complex (after all, it's completely transparent to anything accessing it). ADB probably has commands to make links, terminal emulators in Android definitely can. I think the problem you face is making sure the mountpoint, path, etc are exactly the same both in SS and Android.
Probably better to just do both the mounting and symlinking under Android, so you can be 100% sure that everything matches. We already know /cache/ is unused most of the time under LP, and can (probably) even be unmounted while booted if needbe; why not experiment with it, rather than going straight for the other more important partitions, until you're sure what you're thinking will work?
Edit: Wikipedia has a big ol' writeup on symlinks under various systems, looks like a fun read.
rblanca said:
I believe that it's impossible because symlinking "works" after kernel is loaded and safetrap take place (is loaded) before a kernel is loaded....
Click to expand...
Click to collapse
I guess then this could be implemented in some early booting stage of the system by some custom .zip being patched over, kind of the way Mentor.37's ramdisks are. Unfortunately I don't have nearly enough knowledge to do it.
What I hope could be done more easily is altering SS to maybe use not only shared cache but shared data as well - then webtop could be used for safe system, leaving more then enough space for it, and we still would have fairly usable 3.2 GB data for it. Maybe we could even assign preinstall as stock data? @Mentor.37, I'd really love to hear your opinion on this, or maybe even get your alternated safestrap's source so I could try it myself
Sorry guys, I'm dropping this. I tried CM12 in stock slot and it doesn't help the system as much as I hoped for, so there's no need for this from my side.
I also mistook the process of installing ROM in Stock. I thought I have to upgrade the stock system to the new ROM in order to keep Safestrap in it, but it turns out it's independent and when "wiping" stock /system it leaves the Safestrap there, so I can easily do a clean install of a new ROM in the stock slot
LuH said:
I tried CM12 in stock slot and it doesn't help the system as much as I hoped for, so there's no need for this from my side.
Click to expand...
Click to collapse
About that, could you compare the difference regarding performance between CM12 on the safe slot and CM12 on the stock slot?
I currently got it running on safe slot but I'm thinking about trying to install it to stock slot, now that I sold my Lapdock and don't need Weptop mode anymore.
But I only would do it if it increases the performance of the D4.
Shani Ace said:
About that, could you compare the difference regarding performance between CM12 on the safe slot and CM12 on the stock slot?
I currently got it running on safe slot but I'm thinking about trying to install it to stock slot, now that I sold my Lapdock and don't need Weptop mode anymore.
But I only would do it if it increases the performance of the D4.
Click to expand...
Click to collapse
I don't really remember unfortunately, been running it from stock slot for a while now. Before it definitely was way more laggy than now, but that's also when CM12 for D4 was in a VERY early phase.
It definitely increases the performance, I'm just not sure how much. I don't see any reason why leave original system in stock slot though, so no reason to run CM from the safe slot. I don't like the idea of mounting the ext fs with system running from it from fat storage, it's bound to generate some unnecessary overhead.
In case of any major screw-up, sbf is your friend and AFAIK can't get messed up itself It's a good idea to have the factory cable available though, just in case it for whatever reason dies on you with low battery.
Ok, still good to know, thanks! What's sbf?
Well when I got my D4 a few months ago, I thought installing on the stock slot would be dangerous (in terms of bricking) and since I had the Lapdock, I wanted to keep the stock ROM.
But since then I've read that many users have CM12 running on stock slot, so now I want to do that, too. It's just so annoying when the whole phone freezes for half a minute or so and I think that's mostly due to the limited memory (although I have 170-300 MB free most of the time).
Do I have to consider anything special or different while installing than on an install on safe slot?
Shani Ace said:
Ok, still good to know, thanks! What's sbf?
Click to expand...
Click to collapse
see
Q12: What is a SBF?
Shani Ace said:
It's just so annoying when the whole phone freezes for half a minute or so and I think that's mostly due to the limited memory (although I have 170-300 MB free most of the time).
Click to expand...
Click to collapse
Same here, I suspect it's also connected with throttled data transfer requests of multiple apps at once, but the RAM is IMO the biggest factor. In Linux RAM is almost always full and the "free" space is occupied by cache (filesystem cache or whatever else app's cache) ready to be deleted - maybe the phone is stuttering when freeing the "free" space for other use.
Weird is that my brother with almost vanilla L 5.1 on Nexus 4 has system consuming about 100M less RAM than my CM12 - device-specific drivers maybe?
Shani Ace said:
Do I have to consider anything special or different while installing than on an install on safe slot?
Click to expand...
Click to collapse
If you mean on stock slot, just remember that you need to have some system installed there even in order to boot into safestrap - delete old, install new and ONLY then reboot, otherwise you're facing sbf Learned the hard way It doesn't brick your phone (meaning you can unbrick it), but it's lengthy and annoying...
@sd_shadow: Thanks, now I know. Feels kinda stupid having asked one of the FAQ's - can't remember when that happened before.
LuH said:
Same here, I suspect it's also connected with throttled data transfer requests of multiple apps at once, but the RAM is IMO the biggest factor. In Linux RAM is almost always full and the "free" space is occupied by cache (filesystem cache or whatever else app's cache) ready to be deleted - maybe the phone is stuttering when freeing the "free" space for other use.
Weird is that my brother with almost vanilla L 5.1 on Nexus 4 has system consuming about 100M less RAM than my CM12 - device-specific drivers maybe?
Click to expand...
Click to collapse
Ah that's interesting, didn't know that about Linux before. Well I always imagined that when there's little memory left, the drive somehow gets slowed down because there would'nt be enough space for some temp files or executions. But I don't really have a clue.
On the other hand, different devices showing different and inconclusive results like that is something I already experienced many years ago. ^^
LuH said:
If you mean on stock slot, just remember that you need to have some system installed there even in order to boot into safestrap - delete old, install new and ONLY then reboot, otherwise you're facing sbf Learned the hard way It doesn't brick your phone (meaning you can unbrick it), but it's lengthy and annoying...
Click to expand...
Click to collapse
Yeah I know, I had read about it before. But you can't really miss all those hints everywhere, so I think the community takes good care of spreading that time-saving information.
Actually thanks for encouraging me, because last night I flashed CM12.1 and everything onto the stock slot! Today I installed and configured most of the things I needed (including int/ext storage swap) and I have to say, it really runs better! It might not be as smooth as with a more recent smartphone, but it's definitely snappier than CM12 on the safe slot was (now it's gone and will rest in peace^^). It may sometimes take a few seconds, but most of the time it's very fluid, a great, noticeable improvement.
Additionally, now that I don't have to household with the memory anymore, I installed all the apps that I had left out on the safe slot install and even installed a couple of huge games from the Play Store (NFS:MW, NBA Jam, Batman Dark Knight, Injustice) onto my microSD card and it still runs almost without any hick-ups! I haven't tested the games yet, though.
EDIT: It really seems to have something to do with the amount of memory left on /system. After all that installing I was down to ~ 200MB (which would've been normal on the safe slot) and the phone started lagging a little bit more. But after moving some games and apps to the SD I have more than 500MB 600MB - okay after deleting the cache it's 1,26GB - free on /system and the phone runs smoothly again.
Shani Ace said:
EDIT: It really seems to have something to do with the amount of memory left on /system. After all that installing I was down to ~ 200MB (which would've been normal on the safe slot) and the phone started lagging a little bit more. But after moving some games and apps to the SD I have more than 500MB 600MB - okay after deleting the cache it's 1,26GB - free on /system and the phone runs smoothly again.
Click to expand...
Click to collapse
I guess you're talking about /data, not /system (different partitions, /system is usually read-only and system is installed there with stuff you flash from safestrap, everything else goes to /data or /sdcard). Yup, when /data is becoming full, you're gonna experience some strange behavior.
/data is the first "Internal storage" in Storage settings, /system is not shown there, /sdcard is the second "Internal storage" and /sdcard-ext, or "SD card", is the actual microSD in default CM12 setup. I guess you have the last two switched though.