Related
I recently updated my cappy from Phoenix rising to Continuum following all instructions in the first couple posts except for flashing back to stock. "Including enabling lagfix"
Everything seemed to be running perfect. Rebooted a couple times to see how it behaved, plugged it in and turned in for the night. Seemed to be fine in the morning while I surfed the web, played games, etc. I ended up losing data service (a constant problem I get with custom ROMs that I've never been able to shake) so I rebooted, which normally solves the problem.
Instead, this time appears that all the apps installed in the internal SD card are missing... Weird but whatever. Titanium time and troubleshoot after school. Well, titanium says that there's no backups. Slight panic. Then I think about all my 3 stars from the angry bird series... MAJOR PANIC!
I can access my phone just fine via root explorer but my TiBU folder is empty, I have no games on my SD cards but a lot of other stuff is there including my dropbox and download folders as well as my ROM .zips. It's almost as if random stuff was removed.
Reboot into recovery to fix permissions and delete caches, etc. While I there I checked my backups (Nandroid?) and my lastest one (the one I did prior to flashing) was missing! Even more panicked!
Checked my phone... No luck. So I think that maybe I'll try some sort of undelete program when I get home. Plug the phone into compy and the mount cards options doesn't appear... Reboot to recovery and reflash ROM. No luck. Try to update back to TiBU pro and I notice a new problem. I can't install anything from the market, they just don't download. Tried to install .apks I have stored locally, no luck.
At this point I just want a working phone, screw dem birds, I can always redo all the levels and put music back on. Goto reformat SD cards. The format external is greyed out. Trying to reformat the internal one goes through the motions but there's no update in the available storage.
Flash to Firefly since I had a copy of it on the internal SD. Same issues listed above but with a pretty new interface.
So... Anyone have a suggestion aside from go back in time and buy titanium media sync or for me to suck less? I'm pretty much out of ideas
my first captivate was deleting files on the internal sd (mostly my music folder), returned for exchange. no problems since. hardware issues are fixed by the hardware manufactures!
And if you have other problems NO MATTER what rom you use, then its probably not the rom...
Oops! Sorry, I meant to stress that in the original post: I by no means hold any ROM responsible for the shenanigans my phone is currently experiencing, I originally omitted mentioning any names but decided to include them so I could be as explicit as possible in describing the issues and the steps I took.
Update 1: Attempted Odin3.
Since I'm apparently mentally handicapped, I clicked on "Master clear" instead of "Start". Yellow android guy has been digging a hole on my phone's screen for the last 10-15 minutes with no change.
Don't think that it's suppose to take this long and worried that whatever the SD card issue is may be affecting the master clear but currently too scared to unplug the phone.
Currently chain smoking nervously
----
Update 2: Revenge of the unborking
Unplugged phone and removed battery since master clear was clearly not working
Powered it back up and Odin -> Flash to stock
Stock working but unable to load SD cards
Rebooted a couple times -> problem solved
Mounted SD as USB card
Recurva -> Recovered TiBU folder.
Rooted phone
Reinstalled Clockwork mod
Reflashed Firefly
Installing stuff from the market is still a bit wonky with a custom ROM which is odd since I could install stuff with a stock rom but at least things are progressing
That's cool you got your stuff back. Now make a copy of it on your computer!! Now its just a call to att to get it replaced cause it's a hardware issue for sure.
Oh I'm sure you figured this out but master clear doesn't do anything in download mode, that works when the phone is actually booted.
master clear works booted with debugging on!
Yep, looks like installing stuff from either the market or from the SD card is hit or miss depending on time of day, prevailing winds, or the phase of the moon. Got some stuff installed but now nothing will go on the phone.
Going to complain to Samsung directly to see where what that gets me. Bought the phone used after my last android bit the dust while I was still on contract. Ended up getting a cappy since you could unlock it manually and was unaware that you were stuck on edge service. Wish me luck!
Boot into recovery
Onix Speed Features
LAGFIX options
Enable lagfix: Convert Data to Ext4
Convert SYSTEM to Ext4 /RFS
YES
Go back twice
Reboot System Now
EXT4: Convert to EXT4 (wait for the conversion to complete)
After reboot choose YES (for the rest of partitions to be converted)
Wait for the welcome screen and from the power menu reboot to Recovery
ONIX Speed features
ROOT / install superuser
Simple: Install busybox
Scrool to Yes - apply root to device and select it
Go back twice
Reboot system now
Click to expand...
Click to collapse
I think that I may have borked up my phone when doing this. I used the onix recovery to set everything back to rfs to no avail. I am still unable to install any apps or format the SD cards. Any advice? Currently on hold with Samsung support but apparently I am having a hard time convincing them that Hawaii is part of the United States and that we do in fact have UPS on this island.
Hi there,
So my N1 is rooted and has SuperOSR rom installed. The native app2sd that comes with the rom failed to work, so I disabled it and went back to the method I was using on CM7, Link2sd. I need a method to move apps/cache/lib files to sd-ext, as the tiny internal storage on the N1 is insufficient to hold even a 10th of the apps (and their data) that I have installed. And Link2sd has, at least in the past, been the perfect option to do so.
At first, all seemed well after installing and setting up Link2sd. Mount scripts were created with no problems, apps/cache/lib files all moved over to sd-ext without a hitch. Everything was going really well. Until I rebooted. Then, all hell broke loose.
The problem is this - for some reason, the second partition (sd-ext) is not being mounted during boot time. I'm not sure why, as this is exactly what the Link2sd mount scripts are supposed to accomplish. A Link2sd "mount warning" notice confirmed this problem, saying that "since 2nd partition was not mounted during boot time, linked apps will be invisible to the system until quick reboot". Indeed, every app that I had linked was not visible to the system, and most widgets on my homescreen showed only the message "problem displaying widget".
Luckily, a way to temporarily fix this is by simply quick-rebooting the rom. This will get the linked apps to show up again. But the problem is, widgets are still dead, input method gets reset (goes back from Swiftkey to native Android keyboard), and SMS gets reset back to the standard android SMS app. Of course, all of this can be changed back, but it takes time and effort to load each individual widget and restore each individual input/sms setting. It's really not practical every time you have to reboot your phone that you have to:
1. Quick-reboot the rom
2. Change input method back to Swiftkey
3. Manually restore every widget on your home screens
4. Change sms app back to Go sms.
So, my question is, how do I avoid having to do all this? I've already tried the "re-create mount scripts" option on Link2sd, but it doesn't matter. Still have the same errors upon rebooting phone every time. I'm pretty sure this means that the Link2sd mount scripts are either not being created correctly, or are being deleted every time the phone reboots. How do I fix this? Trying to get in contact with the developer of the app (bakpinar) has proven unsuccessful.
Does anyone know of any other scripts that I can flash/install that will successfully and consistently mount the 2nd partition (sd-ext) during boot time? I'm fairly certain that this is all I need, as everything else with Link2sd has been working correctly. Thanks in advance for any advice!
Ok, so since I haven't gotten any responses on this, I'm going to attempt two methods that i THINK might remedy this issue. The first one is this:
Method 1:
1. Full wipe and reinstall of SuperOSR rom
2. Format sd-ext to ext3 filesystem (found out that rom's native app2sd program wouldn't work due to my sd-ext partition being FAT32)
3. Enable rom's native apps2sd option upon booting.
4. Reboot
5. Install Link2sd from market, enable dex/lib file linking ONLY (native apps2sd program only moves app files, not dex or lib). Going to be interesting to see what link2sd says about the mounting scripts...
6. Reboot, collect results.
The 2nd method I'm going to try is this.
1. Full wipe and reinstall of SuperOSR rom.
2. Flash DTAPPS
3. Boot into ROM
4. Download and install test applications
5. Collect results
I'm not sure if either of these methods will work, however I know the 2nd method worked for CM. I will update a bit later as to which method (if any) fixed the issue. Sorry for the double post.
I commented to the ROM cook nelo360 a while back that there are some strange sd-ext mounting issues. If you look at the dmesg as it boots, it does post some strange error messages. Essentially, ext3 mounts as ext2, and ext4 mounts as ext3. Despite it not mounting as the proper format type, it still works.
Since the ROM is pulled off of AOSP, as CM is too, sort of, much of the same apps2sd apps probably work decently well.
Definitely need an ext3 or ext4 partition. As I'm understanding your post, that did not happen initially, and is crucial to many apps2ext to work, including the built-in one.
Really? Ext4 as 3 and ext3 as 2? Well that would explain why Link2sd was having issues. Hmm.
What I ended up doing was fully wiping the phone, flashing the rom, and then immediately afterwards flashing DTAPPS. Using the GUI interface found on the market, I moved apps to sd-ext and cache to sd-ext as well. The result has been mixed. While there was noticeably more space initially to install apps (something like 190mb internal), that space has declined at almost as fast a rate as when I had no apps2ext of any sort installed at all. This makes me think that while DTAPPS successfully moved some of the initially installed apps over to the sd-ext, it hasn't been moving any new ones i've installed or their cache files. I tried re-moving apps/cache with the gui interface and by using the old-fashioned terminal emulator method, but had no success. Still looking at about 100mb free space on internal. Considering that I only have about 1/4 of the apps installed that I usually have installed on my phone at any given time (I use A LOT of apps), it's become apparent that soon I am going to run out of space again.
As I can't find any method to fix this, I'm afraid I'm going to have to call it quits with this ROM and try something else. Which is a real shame, because stability-wise this ROM beats Cyanogenmod and other ROMS I've tried hands down, while not sacrificing many features. I guess for a user who doesn't use a lot of apps or need a lot of space for them, this ROM would be ideal. Unfortunately, I'm not that type of user.
One problem I've found is that with any automatic apps2sd/ext system is the control of what is actually on the SD vs. internal memory is hard to work out.
With the built in apps2sd, which you seem to have trouble with, not every app was transferred to ext. I found that with the built in system, my internal memory kept dropping until it hit 25 mb or so. However, it never really dropped below that. Everything I kept installing probably went to the ext partition. I installed a lot of apps, and it wasn't an issue. (But you're right, it may not be as many as you want).
I didn't have a great way to check this though. Root explorer showed both the data/apps/ folder and the sdcard/ext folder linked together, so it just listed everything together. I'd have loved a way to actually manually transfer whatever apps were on internal memory to ext, but never found an easy way to do so, or even to confirm what was in which directory.
So even though it looks like the internal memory is steadily and quickly dropping, if you continue to install, and have the two directories appropriately linked (sorry, I don't know what the difference between all the different kinds of scripting apps2sd are), I don't think you'll run out of space as quickly as you think you will.
Hello,
With the issues I was having with the CM 10.1 nightlies, much as I would like to stay, I decided to install the Minimoto 1.7 ROM into the second ROM slot (created with Safestrap 3.05). First, let me say "wow!" I never thought I would see this much speed and available RAM on my Droid 3. Thank you very much, thingonaspring.
For the most part, everything is working great *except* access to both the sdcard (internal) and sdcard-ext (external) storage areas. I read many posts in the Minimoto thread and searched around but nobody else appears to have encountered this which I find rather odd.
After the initial install and after reboots, these areas were still not accessible. I finally ran the terminal emulator and found that, for some unknown reason, they were *not* mounted. I *did* find the internal storage (/dev/block/emstorage) mounted at /ss but not at /mnt/sdcard. I became root using "su" and did the following:
# mount /dev/block/emstorage /mnt/sdcard
# mount /dev/block/mmcblk0p1 /mnt/sdcard-ext
Now I can access them along with all of the files I previously had there. The included file manager, when started, presents buttons for "Internal Storage" and "SD", but it still complains that internal storage is not mounted. It will allow me to access the SD card, though.
Under Settings->Storage Settings, everything under "Internal storage" and "SD card" says "unavailable" and both the mount and format buttons are grayed out. Yet, under the "Windows Media Sync" heading, I *can* choose between internal and SD *and* it even shows the correct available/total space values.
Why were these not mounted to begin with? Is mounting them manually an acceptable solution? If it is, where do I put this information so that it occurs at boot like it should (there is no /etc/fstab on Android)? Did I perhaps do something wrong when installing this ROM, maybe because I used ROM slot 2 instead of 1 (which still contains the most current CM 10.1 nightly)?
I really want to get this resolved because, so far, everything else appears to work wonderfully. Even 3g access, which I still haven't gotten working with CM 10.1.
--John Gruenenfelder
I've been running Minimoto for months and both /sdcard and /sdcard-ext are mounted at bootup for me, always, just like stock.
So, I wish I could tell you why, but I cannot.
I guess what I would do is start over. Reboot into Safestrap, remove that second slot and recreate it. Flash the ROM and restart the phone. Do not wipe data/factory reset after flashing the ROM or you will be missing some files (basically, some files required by the customized initial setup application.)
It seems to be fixed! See below for (perhaps) how...
Okay, I gave this a try. Rather than wiping ROM-slot-2, I had enough free space to create slot-3 and I reinstalled Minimoto 1.7 there. Also, this time I downloaded the zip file on my PC and transferred it over rather than downloading it directly onto the phone. Using the UNIX "cmp" tool told me the two files were identical, but I still used the "new" one. It installed fine and I did *not* perform a data wipe.
Unfortunately, same issue. When the device starts I can see the "Preparing XXX storage" messages appear in the notification bar for both internal and SD storage. There are no error messages, but it also did not actually do anything. Then, using the terminal emulator, I gave a long read through the dmesg output. I am more familiar with the kernel messages one sees when booting Linux on a PC, but I still did not see anything unusual.
So, back into Safestrap recovery. This time I tried something different. First, I noticed that the Safestrap file manager *can* see both storage areas and in the locations where they ought to be. This is not new, actually, it has always been the case. Second, I uplugged the USB cable. I have been using it for charging (of course), but at present it was plugged into my laptop and not into the wall charger. Depending on how the mounting occurrs and the exact mount order, I thought this might interfere. Thirrd, and finally, I used the "Fix Permissions" button available in Safestrap on ROM-slot-2 where I had first intalled Minimoto.
After doing these two changes I rebooted the device back into ROM-slot-2. Surprise! I once again saw the "Preparing" messages in the status bar except this time it really worked. The two storage locations are available where they should be and I an access the data just fine. Even the "Storage properties" screen in Settings shows both as mounted with the correct available/total space values given.
Since a plain reboot did not work previously, I have to assume one of the two changes I made fixed the problem, though, since I did both at the same time, I cannot be sure which fixed it.
Now I can get back to enjoying the impressivee speed from Minimoto while I wait to see if (or perhaps when) either the 3g or HW keyboard ALT-key issues are fixed in CM 10.1. Of course, given how much slower CM 10.1 operates (by virtue of using *much* more RAM than Minimoto), I think I might find it very difficult to switch.
--John Gruenenfelder
If you've been trying to hoot while plugged into your laptop I can see it causing issues as when usb mass storage is active, the device can no longer see the sd cards. That is why we have a separate data partition for apps and app data. So if the computer is trying to mount them and denies the phone the ability to mount then I could see issues arising
Sent from my XT860 using xda premium
I posted this on rootzwiki, but I'm hoping someone here will help guide me back.
I have CM9 installed, which was working great except that I kept having "not enough memory" errors when trying to install apps from the Market.
I went to the CM7 sdcard problem fixes thread, found here:
http://rootzwiki.com/topic/13277-cm7-fixes-for-sdcard-issues/
These fixes work for CM7 and 9, so there is no compatibility issue there.
I attempted to expand the data partition by 1gb by flashing the correct .zip. However, after waiting 1.5 hours, with no change in the screen, I was forced to reboot it. I don't think I was too mistaken for thinking otherwise. No error message was given.
Now:
1. It reboots into CM9 okay, except the "checking SDcard" sign is on forever. Thus no access to the SDCard.
2. It won't reboot into WebOS anymore. It stays at the hp icon. This is most concerning to me, because to me it implies that something more than then Android install is broken now.
3. In Clockwork Recovery, it won't allow me to restore! Selecting that option just freezes CWM. However, it will allow me to browse the sdcard contents when selecting "install from zip"
4. From CWM, I can mount USB access and see all contents of the SDCard.
5. I did some searching, and one post suggested removing fsck_msdos from system/bin. I did this, which allowed me to access the SDCard in CM9 as this circumvented the SDcard checking. This obviously is not the right solution, so I restored it.
Next steps please?
I've got backups so the data isn't so important.
I think the sdcard partitioning is wonky due to the aborted memory expansion attempt, so I'm not sure running ACMEuninstaller will fix that.
I'm thinking I attempt to run ACMEUninstaller first, followed by WebOSdoctor if it won't boot into WebOS?
Take a look at this guide : http://forum.xda-developers.com/showthread.php?t=1426244
Yup, ended up doing that and looks like it's doing well.
Basically jacked up the storage partition so badly there were an infinite # of errors. Because WebOS uses that same storage for some of its files, couldn't boot either.
I've had to do it 3 times already.
It's a big PITA, but it works....... If your partitions get fracked, I've found this to be the best option.
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.