Related
This has been updated to be deodexed+root+busybox only (though it still supports JAC kernel out of the box). At this point there are so many different lag fixes that it's hard to keep up with them all.
What it does have:
ROOT
No .odex files (deodexed)
Newest Busybox
ext manipulation files and libs, so it makes it easier to e2fsck or tune2fsck if you want ext4.
Also thanks to eugene373 for his work in establishing a baseline update.zip without which this would have taken a great deal more work.
Should work in clockwork, doesn't seem to need a wipe. If you have problems, use regular recovery, just rename it to "update.zip" on the root of your sdcard and it should flash just fine.
WARNING:
This should be completely safe. Nonetheless, should loss of job/loss of fertility/nuclear war ensue, I am not responsible.
Instructions:
1. Load the .zip file onto the root of your internal SD card (/sdcard)
2. Using Clockwork recovery, do "Install zip from SD card", then "Choose zip from sdcard", choose the VibrantDeodexed.zip, and choose "Yes"
2b.(ONLY If you don't have Clockwork) rename the download to "update.zip" and place it on the root of your sdcard. Then reboot into recovery and choose "Update packages".
3. (Optional) Flash JAC's kernel with ODIN using the directions specified HERE It is more stable and gets better benchmarks but there do seem to be some issues with the screen taking a while to wake up.
http://www.getyourboneon.com/VibrantDeodexed1_2.zip
NOTE: The first boot takes a long time because it has to dexopt stuff.
Version 1.0:
Just stock and rooted w/busybox
Version 1.1:
Uses the latest version of busybox and comes with support for JAC kernel out of the box (no need to flash the init.d update.zip and supersedes my method if his kernel is flashed.)
Version 1.2:
Updated busybox, added ext tools. Removed all lag fixes, though it will still work with the JAC kernels.
There are so many lag fixes out there at the moment that I didn't want to "lock in" people to a particular one.
Part of the high quadrant score is the 90 million triangles/sec. The data script boosts the data score.
Sent from my SGH-T959 using XDA App
what is the ext hack? and how does it make the phone faster?
the ext hack puts the data and dalvik cache on the sdcard on an ext2/3 partition...
it brought my quadrant score from 850-950 up to 1400-1500
its like apps2sd but the apps part is still on the phones internal memory...
original link is here for the hack--http://forum.xda-developers.com/showthread.php?t=739647
anomalous, thanks for all your hard work...
so if we get a good deodexed rom, someone could compile JIT for our 2.1 right?
junkdruggler said:
the ext hack puts the data and dalvik cache on the sdcard on an ext2/3 partition...
it brought my quadrant score from 850-950 up to 1400-1500
its like apps2sd but the apps part is still on the phones internal memory...
Click to expand...
Click to collapse
why does the phone run faster with the data stored externaly? or is it because of the partition type?
im not quite sure, I would have figured our internal mem had a faster transfer rate than an sdcard, but Im on a class 2 and still getting better results... so it cant be a faster transfer rate...
@freedom: put simply, EXT formats run way faster than Fat32, which is what the rest of the storage is.
wiki: EXT3 (common format) and ext4 (latest)
edit: better explanation here
However, I'd most love to see either one of the internal storage (app storage or the other internal) finding a way to be put into EXT3, as that would probably run better than any sdcard.
Just so everyone Knows, the Format via the update script don't work, still trying to find the correct command for it....
But, in clockworkmod, just format the system / data / cache partition's before flashing.
designerfx said:
@freedom: put simply, EXT formats run way faster than Fat32, which is what the rest of the storage is.
wiki: EXT3 (common format) and ext4 (latest)
edit: better explanation here
However, I'd most love to see either one of the internal storage (app storage or the other internal) finding a way to be put into EXT3, as that would probably run better than any sdcard.
Click to expand...
Click to collapse
Er, the internal storage is "rfs", samsung's proprietary fs. (And the read/write speed of fat32 tends to be a little faster than ext2, and TONS faster than ext3/4 - journals slow it down in exchange for stability after crashes)
The increase in speed is just that - faster underlying hardware. The onboard "sd card" (same "disk" that /data is partitioned out of) is heartbreakingly slow.
Disconn3ct said:
The increase in speed is just that - faster underlying hardware. The onboard "sd card" (same "disk" that /data is partitioned out of) is heartbreakingly slow.
Click to expand...
Click to collapse
Is there an app to test thr transfer speed on the phone? I ask because I have moved my data/dalvik to ext3 on a class 6 sd card. When I benchmark reads from Linux the speed and seek time between internal and my sd are not that great yet the actual performance of the phone is as different as night and day.
I wonder if this is more an issue with the rfs implementation than a hardware speed issue. My other thought is that maybe the benefit comes from having a separate I/O lane for loading data/dalvik. Not sure the hardware actually supports multiple/parallel I/O but it's a theory.
Sent from my SGH-T959 using XDA App
How did you de-odex the the core.jar? I've unodexed the whole thing myself as well, as well as optimize the heck out of every jpeg, png and gif inside the apks (excluding 9.png's of course) but I'm having an issue deodexing core.jar. Did you just replace it with the one from the deodex'd SGS ROM?
FastKatt said:
Is there an app to test thr transfer speed on the phone? I ask because I have moved my data/dalvik to ext3 on a class 6 sd card. When I benchmark reads from Linux the speed and seek time between internal and my sd are not that great yet the actual performance of the phone is as different as night and day.
I wonder if this is more an issue with the rfs implementation than a hardware speed issue. My other thought is that maybe the benefit comes from having a separate I/O lane for loading data/dalvik. Not sure the hardware actually supports multiple/parallel I/O but it's a theory.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I'll see what I can do to test it out this afternoon. (If you want to jump the gun, what I'm figuring is finding a static-linked arm version of bonnie++ or similar. Booting recovery, mount data or sdcard - not both - and test. Reboot recovery, test the other one. Maybe test dbdata and external sd as well, but the interesting numbers will be the first two - onboard-with-rfs and onboard-with-vfat..)
ivanmmj said:
How did you de-odex the the core.jar? I've unodexed the whole thing myself as well, as well as optimize the heck out of every jpeg, png and gif inside the apks (excluding 9.png's of course) but I'm having an issue deodexing core.jar. Did you just replace it with the one from the deodex'd SGS ROM?
Click to expand...
Click to collapse
Honestly, used the ROM kitchen for most of it; it uses a brute-force approach to sort out dependencies. Only one I had to do manually was TouchWizCalendar.apk (because it needed both twframework.jar and com.google.android.maps.jar). I'll work on getting the update script working during work later today.
anomalous3 said:
Honestly, used the ROM kitchen for most of it; it uses a brute-force approach to sort out dependencies. Only one I had to do manually was TouchWizCalendar.apk (because it needed both twframework.jar and com.google.android.maps.jar). I'll work on getting the update script working during work later today.
Click to expand...
Click to collapse
Which ROM kitchen? I used my own script. Does the ROM boot up and run doing it that way? Should be interesting to play with.
Hmm, got the update script working almost perfect, but now it causes crashes. Seems to be missing dbus.conf.
OP updated - it works.
I did something very noobish.
I formatted the cache, system and data and forgot to throw the update.zip file onto the internal sd card prior to doing this. I can get into the stock recovery but as far as rebooting the phone to put the update on the internal storage I can't do that. I am able to take out the 2g memory (avatar) and load the update.zip on there but, of course, the stock recovery won't recognize that.
Is there a way to put the update.zip onto the internal memory in the position that I am in? Is there anything I can do?
I think I just made a HUGE no-no.
Any help would be greatly appreciated.
theMAGNUM said:
I did something very noobish.
I formatted the cache, system and data and forgot to throw the update.zip file onto the internal sd card prior to doing this. I can get into the stock recovery but as far as rebooting the phone to put the update on the internal storage I can't do that. I am able to take out the 2g memory (avatar) and load the update.zip on there but, of course, the stock recovery won't recognize that.
Is there a way to put the update.zip onto the internal memory in the position that I am in? Is there anything I can do?
I think I just made a HUGE no-no.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Have you tried connecting your phone to your computer while at the recovery, and see if you can access it via ADB?
ArbitrageMan said:
Have you tried connecting your phone to your computer while at the recovery, and see if you can access it via ADB?
Click to expand...
Click to collapse
No adb shell doesn't find my device
Just got my Nook Color tonight. I booted it from a CWM microSD card, installed CM 7.1 stable, gapps, and ran ROM Manager to install CWM to internal memory.
When I go to Menu, Settings, Storage, under the 'Internal Storage' heading, it says "Total space" of 5.09 GB and "Available space" of 4.68 GB. (One app installed so far)
Looking farther down the screen, it shows /mnt/eemc to have 1.00 GB of space.
Is there a way to combine them so that I have 5.68 GB of usable internal space to install apps to? Also, are those two the full available capacity of the eMMC storage? If not, can it be enlarged to maximum?
Also, further down the screen, it shows /mnt/usbdisk, with no space. Should it be left intact, or can it be safely removed to limit my confusion?
Thanks!
+1 to your question.
I'm gonna use my NC only as a tablet not any book reading so I don't think that 1GB is required.
Still let's wait for a dev. to give expert advice about this and possibly a how-to...
I would leave /mnt/usbdisk alone as it will be useful if you decide to use flash drives through nook tweeks in the usb section. As for the emmc data area, you can store data there with no problem if you are not going to use the nook as an e-reader.
By downloading the nook tweeks app, you will have access to the micro usb port (through an adapter) to transfer data between the nook and a flash drive or (using a powered hub) a card reader. You can also transfer data between the nook and a camera to directly save photos to the nook or view them. Usb host mode opens the nook up to another level and makes it a very functional tablet.
I use my nook with a digital camera on photo shoots so that I can preview my shots on a larger screen than that of the camera. You can check out my threads here concerning host mode. PM me if I can be of any assistance.
Sent from my NookColor using Tapatalk
SweetBearCub said:
Just got my Nook Color tonight. I booted it from a CWM microSD card, installed CM 7.1 stable, gapps, and ran ROM Manager to install CWM to internal memory.
When I go to Menu, Settings, Storage, under the 'Internal Storage' heading, it says "Total space" of 5.09 GB and "Available space" of 4.68 GB. (One app installed so far)
Looking farther down the screen, it shows /mnt/eemc to have 1.00 GB of space.
Is there a way to combine them so that I have 5.68 GB of usable internal space to install apps to? Also, are those two the full available capacity of the eMMC storage? If not, can it be enlarged to maximum?
Also, further down the screen, it shows /mnt/usbdisk, with no space. Should it be left intact, or can it be safely removed to limit my confusion?
Thanks!
Click to expand...
Click to collapse
Hey there, I know long time but iI have some info to share since I'm having the same configuration as yours.
The 'Internal Storage' you're seeing isn't exactly the emmc. Its just that cm7 doesn't know its put on an SD. And it thinks the second or third partition of the SD (i.e. cm7 system partition) is internal.
Also that /mnt/eemc is the actual internal memory and thus these 2 can't be linked. However, the nook has another 5gb emmc internal partition callednmedia which you can possibly combine with emmc.
Sent from my NookColor using Tapatalk
there are many threads about the NC partition layout and changing it. do a search. the 5g partition basically won't be used by your cm7 NC. the apps will go on the 1g. I repartitioned mine for 4g instead of 1g and 2g for /emmc. then you can set cm7 to swap the /emmc and /sdcard and then use the NC without an SD installed.
mr72 said:
there are many threads about the NC partition layout and changing it. do a search. the 5g partition basically won't be used by your cm7 NC. the apps will go on the 1g. I repartitioned mine for 4g instead of 1g and 2g for /emmc. then you can set cm7 to swap the /emmc and /sdcard and then use the NC without an SD installed.
Click to expand...
Click to collapse
I was thinking something else.....
I wanted to merge internal data and media so as to get combined partition. I'm running CM7 off the SD card so I don't need to switch them. I was just thinking of merging them.
Sent from my NookColor using Tapatalk
therkr said:
I was thinking something else.....
I wanted to merge internal data and media so as to get combined partition.
Click to expand...
Click to collapse
Yes, I understand that's what you want to do. However, those partitions are not contiguous space. Search on Nook Color partitions and you will quickly see why.
Specifically, look here:
http://forum.xda-developers.com/showthread.php?t=1094371
which links to here:
http://forum.xda-developers.com/showpost.php?p=13971291&postcount=110
/dev/block/mmcblk0p6 is the "data" partition
/dev/block/mmcblk0p7 is the "cache" partition
/dev/block/mmcblk0p8 is the "/mnt/emmc" partition
You are wanting to combine "data" and "/mnt/emmc". Problem is the "cache" partition is stuck in between them.
The other problem is your NC uses these two partitions for different things.
I think the suggestion I made before, which is to repartition for 2GB+4GB as in the first link, then do Settings -> CyanogenMod Settings -> Application -> Use internal storage to get them to swap, is the best, simplest solution with the lowest risk. This uses the 2G partition for whatever normally is used for /sdcard by most apps (downloads, misc. files, temp storage, etc.) and 4G partition for your apps, and leaves your whole SD card for use solely for your side-loaded media content. This schema will not interfere with further CM updates or unnecessarily change the default partition scheme for which most of the devs are writing code.
If you want to become a Linux & Android master of partitioning and storage management, then you can probably implement a more custom scheme. In my last job I was a software engineer working on a Linux-based network-attached storage appliance and I wrote most of the system code dealing with disk and partition management, so you could say I know a lot about it, but still I chose the easy path for my NC.
mr72 said:
If you want to become a Linux & Android master of partitioning and storage management, then you can probably implement a more custom scheme. In my last job I was a software engineer working on a Linux-based network-attached storage appliance and I wrote most of the system code dealing with disk and partition management, so you could say I know a lot about it, but still I chose the easy path for my NC.
Click to expand...
Click to collapse
Thanks for the info. But I'm just a highschool sophomore who loves technology. Can't do this unless someone has ever tried (and succeeded) before.
I'll probably use your method when I install CM7 (or CM9) onto emmc.
Sent from my MB502 using XDA App
I have a problem. I have a 4GB sandisk sd card. Yesterday when I was on stock DDKQ8 ( with other apps installed ). After flashing cwm, I partitioned to have 1GB ext on my sd using cwm. Partitioning took unevenly very long time. But after completion, I connected phone to pc & on opening easus partition manager, it did not read any partition on my sd. I ran the partition recovery wizard but with no use. I tried resizing the primary partition ( now it was reduced to 2.67 GB ) but the option was grey ( unavailable ). Then I disconnected phone & flashed sgs2 rom. But during wiping, when I opted the wipe data/factory reset option, my phone got stuck at formatting sd-ext. I took out battery & tried repartitioning sd card via cwm. This time it was a bit faster & I got through the wiping quickly & flashed the rom. Flashed d2ext+ & rebooted. In storage option under settings, I found that my internal memory was successfully extended. I was able to install apps & everything was working normally. Thinking that my sd was back on track, I reconnected phone to pc just to verify that the partition was recognized by it. But to my surprise, easus still showed no partition. Now I'm stuck. How do I delete the partition without having to see it ? Will my sd be permanently restricted to reduced memory ? Please help.
Some additional info :
A couple of days ago my friend had brought a pen drive which contained some important files. On connecting it to my pc, windows asked me to scan & fix. I did, but later on data transfer to/from it got really slow & I saw that windows explorer wasn't responding. As he was from the neighbouring town, we couldn't afford to lose the data & somehow after random connecting & disconnecting, I managed to copy the files onto my pc. I formatted the pen drive but the slowpoke problem prevailed. And now I wonder if this in anyway has troubled my sd. Doubting this, I formatted my C:/ drive & reinstalled my windows, in case there were viruses. But the problem was still the same. Thought there might be viruses in my backup files. Ran a boot time scan using avast! for over 2hrs. Found a couple of minor pups. Deleted them & rebooted. But still the same. Unrecognized ( not shown at all, just the primary partition is being shown ) partition by easus. All the drivers are definitely correctly installed by me. I tried copying files to another sd of mine. Even this was awefully slow. Can anyone help me out ?
Sent from my GT-Xperia S using xda premium
Venomous Viper 119 said:
I have a problem. I have a 4GB sandisk sd card. Yesterday when I was on stock DDKQ8 ( with other apps installed ). After flashing cwm, I partitioned to have 1GB ext on my sd using cwm. Partitioning took unevenly very long time. But after completion, I connected phone to pc & on opening easus partition manager, it did not read any partition on my sd. I ran the partition recovery wizard but with no use. I tried resizing the primary partition ( now it was reduced to 2.67 GB ) but the option was grey ( unavailable ). Then I disconnected phone & flashed sgs2 rom. But during wiping, when I opted the wipe data/factory reset option, my phone got stuck at formatting sd-ext. I took out battery & tried repartitioning sd card via cwm. This time it was a bit faster & I got through the wiping quickly & flashed the rom. Flashed d2ext+ & rebooted. In storage option under settings, I found that my internal memory was successfully extended. I was able to install apps & everything was working normally. Thinking that my sd was back on track, I reconnected phone to pc just to verify that the partition was recognized by it. But to my surprise, easus still showed no partition. Now I'm stuck. How do I delete the partition without having to see it ? Will my sd be permanently restricted to reduced memory ? Please help.
Some additional info :
A couple of days ago my friend had brought a pen drive which contained some important files. On connecting it to my pc, windows asked me to scan & fix. I did, but later on data transfer to/from it got really slow & I saw that windows explorer wasn't responding. As he was from the neighbouring town, we couldn't afford to lose the data & somehow after random connecting & disconnecting, I managed to copy the files onto my pc. I formatted the pen drive but the slowpoke problem prevailed. And now I wonder if this in anyway has troubled my sd. Doubting this, I formatted my C:/ drive & reinstalled my windows, in case there were viruses. But the problem was still the same. Thought there might be viruses in my backup files. Ran a boot time scan using avast! for over 2hrs. Found a couple of minor pups. Deleted them & rebooted. But still the same. Unrecognized ( not shown at all, just the primary partition is being shown ) partition by easus. All the drivers are definitely correctly installed by me. I tried copying files to another sd of mine. Even this was awefully slow. Can anyone help me out ?
Sent from my GT-Xperia S using xda premium
Click to expand...
Click to collapse
you can cwm partitions by wiping data and other things.
I recommend you to use mini tool partition wizard to make partitions
limxyz said:
you can cwm partitions by wiping data and other things.
I recommend you to use mini tool partition wizard to make partitions
Click to expand...
Click to collapse
I already know that but thanks for replying anyway ! I some how managed to get back my sd to its full capacity but the data transfer from pc is extremely slow ( just 24kbps !!! ). I tried this on another pc but same result. So I'm sure it should be the problem with the sd itself. I had a 5 yr warranty on it. Will I get a replacement ?
Sent from my GT-S5830 using xda premium
use Magic Partition Wizzard, from Windows
walter11av said:
use Magic Partition Wizzard, from Windows
Click to expand...
Click to collapse
Actually my friend, it doesn't matter what partition tool you use. As long as you know how to use it, you'll get the same results with each but thanks for trying to help !
Sent from my GT-S5830 using xda premium
Hi, I'm new to the SGS after having used a ZTE Blade for a couple of years.
I've got this thing pretty much setup how I want. Running a stripped down CM10.1 nightly with hugemem enabled using the semaphore kernel.
I've swapped the internal and external SD cards by modifying vold.fstab. I needed to do this because I have games that download huge amounts of data to the sd card.
I also have more game apk's than can fit in the phones internal data so some of them are moved to the SD card. Here's where the problem lies.
Clockworkmod doesn't know that the internal and external SD cards are swapped. It has the internal and external labels the wrong way around on its backup and restore routines. Hardly a major problem, but what is a problem is that it's backing up an empty .android_secure folder from the internal SD card.
Is there anything I can do about? Some setting to swap internal and external cards in CWM? Or alternatively get the rom to use the internal sd card for .android_secure despite the sd cards being swapped?
It's not the end of the world because after restoring a rom I can just restore outdated and missing apps using Titanium. I'd just like my backup to be complete if it's possible to do!
Thanks.
Nice question mate, I haven't seen someone with that issue before, may be just because they are happy enough with their swapped memories and don't think about backups. I think that for now you have to use TB to backup your apps correctly and hopefully cwm team will fix that. Have you tried to reinstall recovery?
I only actually noticed it because after switching form the Blade (an ARMv6 phone) to the SGS (ARMv7) I gradually added a load of games to my phone that were now compatible and yet my backups were getting smaller! I noticed the android_secure backup file was 0 bytes and that's when I worked out what was happening - I was moving the bigger stuff to SD and it wasn't getting backed up.
As for re-installing recovery, I switched to the Semaphore kernel and it replaced the recovery with a different one which has the same problem as the CM10.1 version.
Ok, so that's not a solution. The worst part of the story is that folder .android_secure is harder accessible even than any system files and paths. If you find a way to open it you may copy all the apk.s to some safe directory and this way you have at least the installation data of your apps and you have just to reinstall them ( I realize it's not such an easy if they are >100). Better than search the net again or copy from pc. How much easier it would be if we just have to copy apk file of the app to/data/data or .android_secure instead of installing it to get it in your app drawer. XD
A google search found this: http://forum.xda-developers.com/showpost.php?p=31148760&postcount=369
So they've at least thought about this scenario on the SGS2! I wonder if any of the SGS1 devs around here here have fixed this in their recovery without us knowing?
Cool dude, nice find. I think you loose nothing if you try that.
I'm not sure flashing recovery for another model is a good idea? On my last phone you couldn't even use recovery from a different software revision of the same phone hardware!
In any case, isn't recovery part of the kernel on the SGS? Flashing a kernel always seems to change it anyway. Which again, differs from what I'm used to.
I was more hoping this would prompt one of the devs to fix it or point me to one they'd already fixed in the past that I'm unaware of.
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