Develop Bugs

[Q] Is it possible to resize the internal partitions on the Play?

Apologies if this has already been asked elsewhere, but I got no search results on it...
I was checking partition sizes using Root Explorer yesterday, and the following is what I was seeing:
Data: 380MB, 65.11MB free
System: 312.5MB, 83.02MB free
Cache: 225MB, 1.31MB used
This works out at around 1GB of internal storage, and on my phone, over 300MB wasted between system and cache partitions. Is the large cache partition there for downloading all that extra game data, because it seems needlessly large otherwise?
The big question though - is there any way to repartition the internal storage?

Yes there is but you would need some way to instruct s1 boot to use the new partition table, even with an unlocked bootloader we can't do this. Also in the 2.3.4 update /cache/ has been reduced to 100mb.
Sent from my R800i using Tapatalk

AndroHero said:
Yes there is but you would need some way to instruct s1 boot to use the new partition table, even with an unlocked bootloader we can't do this. Also in the 2.3.4 update /cache/ has been reduced to 100mb.
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
Thanks So if I flash any of the 2.3.4 ROMs, I'll have an extra 100MB on my data partition? I'd be happy enough with that...
As for instructing s1 boot to use the new partition table, do you mean there's no way to do this, full stop, or no way to do it YET? Because obviously the 2.3.4 ROMs can do it, so just wondering if it's something the devs may be able to figure out and do in future...

drunkenfcuk said:
Thanks So if I flash any of the 2.3.4 ROMs, I'll have an extra 100MB on my data partition? I'd be happy enough with that...
As for instructing s1 boot to use the new partition table, do you mean there's no way to do this, full stop, or no way to do it YET? Because obviously the 2.3.4 ROMs can do it, so just wondering if it's something the devs may be able to figure out and do in future...
Click to expand...
Click to collapse
Thats the thing, it's just disapeared this other 100mb, they didnt add it to /data/ or /system/ just hid it on a seperate partiton
Afaik there is no way full stop, although we have unlocked bootloaders, we dont have s-off like HTC devices, were unable to modify bootloader Sony on the other hand add diffrent bootloader versions to there stock roms, so it's the latest bootloader that comes with the 2.3.4 roms that has repartitioned /cache/
If you want to free up some space, you may want to try link2sd on the market, it works simlar to apps2sd+ i have over 300 apps on my phone and still have 235mb free thanks to link2sd
https://market.android.com/details?id=com.buak.Link2SD&hl=en

AndroHero said:
Thats the thing, it's just disapeared this other 100mb, they didnt add it to /data/ or /system/ just hid it on a seperate partiton
Afaik there is no way full stop, although we have unlocked bootloaders, we dont have s-off like HTC devices, were unable to modify bootloader Sony on the other hand add diffrent bootloader versions to there stock roms, so it's the latest bootloader that comes with the 2.3.4 roms that has repartitioned /cache/
If you want to free up some space, you may want to try link2sd on the market, it works simlar to apps2sd+ i have over 300 apps on my phone and still have 235mb free thanks to link2sd
https://market.android.com/details?id=com.buak.Link2SD&hl=en
Click to expand...
Click to collapse
maybe they added it into an ext recovery, so maybe we could use CWM with 2.3.4?

AndroHero said:
Thats the thing, it's just disapeared this other 100mb, they didnt add it to /data/ or /system/ just hid it on a seperate partiton
Afaik there is no way full stop, although we have unlocked bootloaders, we dont have s-off like HTC devices, were unable to modify bootloader Sony on the other hand add diffrent bootloader versions to there stock roms, so it's the latest bootloader that comes with the 2.3.4 roms that has repartitioned /cache/
If you want to free up some space, you may want to try link2sd on the market, it works simlar to apps2sd+ i have over 300 apps on my phone and still have 235mb free thanks to link2sd
https://market.android.com/details?id=com.buak.Link2SD&hl=en
Click to expand...
Click to collapse
Thanks, I'll take a look
Do you have 2.3.4? You can use ADB to list the partitions, so you might be able to see where that 100MB has gone...
adb shell
df -h
I get the following:
Code:
Filesystem Size Used Available Use% Mounted on
tmpfs 199.0M 76.0K 198.9M 0% /dev
tmpfs 199.0M 0 199.0M 0% /mnt/asec
tmpfs 199.0M 0 199.0M 0% /mnt/obb
/dev/block/mtdblock0 312.5M 190.8M 121.7M 61% /system
/dev/block/mtdblock3 380.0M 296.4M 83.6M 78% /data
/dev/block/mtdblock2 225.0M 1.3M 223.7M 1% /cache
/dev/block/mtdblock1 10.0M 1.5M 8.5M 15% /data/idd
Or just 'df -h' from a terminal window on your phone...

Code:
df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 177.3M 44.0K 177.3M 0% /dev
tmpfs 177.3M 0 177.3M 0% /mnt/asec
tmpfs 177.3M 0 177.3M 0% /mnt/obb
/dev/block/mtdblock0 312.5M 137.4M 175.1M 44% /system
/dev/block/mtdblock2 380.0M 123.3M 256.7M 32% /data
/dev/block/mtdblock1 101.5M 18.0M 83.5M 18% /cache
/dev/block/vold/179:1
1.9G 1.1G 773.4M 59% /mnt/sdcard
/dev/block/vold/179:1
1.9G 1.1G 773.4M 59% /mnt/secure/asec
/dev/block/dm-0 5.1M 3.6M 1.4M 71% /mnt/asec/com.mojang.miecraftpe.demo-1
This is from my phone running the latest CM.
I cant find the 100 MB here

Azeazezar said:
Code:
df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 177.3M 44.0K 177.3M 0% /dev
tmpfs 177.3M 0 177.3M 0% /mnt/asec
tmpfs 177.3M 0 177.3M 0% /mnt/obb
/dev/block/mtdblock0 312.5M 137.4M 175.1M 44% /system
/dev/block/mtdblock2 380.0M 123.3M 256.7M 32% /data
/dev/block/mtdblock1 101.5M 18.0M 83.5M 18% /cache
/dev/block/vold/179:1
1.9G 1.1G 773.4M 59% /mnt/sdcard
/dev/block/vold/179:1
1.9G 1.1G 773.4M 59% /mnt/secure/asec
/dev/block/dm-0 5.1M 3.6M 1.4M 71% /mnt/asec/com.mojang.miecraftpe.demo-1
This is from my phone running the latest CM.
I cant find the 100 MB here
Click to expand...
Click to collapse
I suppose if it's hidden from Android, then ADB wouldn't see it anyway. And it's actually more than 100MB. More like 123.5MB. Would love to know where it's gone!

[Q] BusyBox Free locked my Nexus memory to read only

I've had BusyBox Free on my Nexus for many months... only there to keep me on the latest version. Well, yesterday it told me about 1.20.2 so I let it install that but it was a big mistake.
The memory is locked at read only now. I can even see last files written to it were...
busybox-stericson
toolbox-stericson
It crashes if I don't quickly put it in airplane mode, for example. I can push and delete files via adb, but that's only fake because once the buffer fills with backlogged changes, the phone crashes. In fastboot, erasing userdata, etc. doesn't really erase anything. Locking/Relocking the bootloader doesn't reallly take effect either, and neither does reflashing recovery. Formatting the internal memory doesn't have an effect, and while restoring a recovery backup goes through the motions, it complains at the end about the memory being read only.
I wrote the BusyBox Free developer an email last night but didn't get a response yet.

I don't know how this is possible.
BusyBox doesn't change anything to read only, except for /system, which is suppose to be read only anyways.
Besides this point, anything Busybox would have done, in regards to remounting partitions to rw, ro, or whatever a reboot would reset these to their defaults.
I suspect something else is going on. Maybe an applet or something of the like has been replaced that is causing this issue, but I have never heard of my installer causing an issue like this.
also, those files you are talking about being written, are written to you SDCard or internal storage which is not a part of your phones system memory.

Stericson said:
... those files you are talking about being written, are written to you SDCard or internal storage which is not a part of your phones system memory.
Click to expand...
Click to collapse
The Galaxy Nexus lumps all its memory in one 32GB pool (internal with SD) which is normally great compared to all my other Android devices. Regardless, writes to any of the filesystems don't appear to get committed from a buffer.
Anyways, thanks for the response. I'm gonna' have to do some more research and hope there's nothing wrong at the hardware layer (eg. write-enable/disable trace on chip). Physically, my phone is pampered and in mint condition.

I would say that's pretty dang good response time from the dev, and on the forum, even.
:good:

consultant.ben said:
I would say that's pretty dang good response time from the dev, and on the forum, even.
Click to expand...
Click to collapse
I agree, Ben. I have to remember this is more of a volunteer effort here, unlike at work where I'm a product engineer with certain response time criteria.

Hmmm, even with the memory being all internal I don't change any of the write permissions on the external storage...
Did you replace any applets?
Did you use smart install or normal install?
Maybe some applet got replaced that otherwise shouldnt have been...
If you run a logcat, do you notice any weird errors....if so, what are they stating?
Also, when your phone crashes, can you give us the actual logcat of the crash?
Also, I try to respond as quick as possible, but I have so little time to dedicate to my own personal applications nowadays

I didn't replace any applets, and have never used your applet manager. Also, normally I wait for your smart install to scan, but I remember I did something abnormal that day and impatiently hit install (ie. normal install) while it was doing its smart scan. It reported successfully installing 1.20.2 though.
Per your request... adb logcat -d -v time > logfile.txt
I put that file on my website at http://ErichMoraga.com/logcat.txt
I pulled the SIM card so I wouldn't have to put it into airplane mode, and got the logcat once the OS loaded after a crash. At first I thought this part was curious...
07-08 12:18:01.234 I/SystemServer( 186): Mount Service
07-08 12:18:01.234 D/MountService( 186): got storage path: /mnt/sdcard description: Internal Storage primary: true removable: false emulated: true mtpReserve: 100 allowMassStorage: false maxFileSize: 0
07-08 12:18:01.234 D/MountService( 186): using emulated external storage
But then I searched on the Internet and noticed other people had that too. This logcat didn't appear to catch the actual crash (I don't see how it could if I'm having a read only memory problem).
I understand we both don't have much free time, being technical people. Normally I'm analyzing logs for customers, so it's frustrating 'shooting my own device. I do appreciate any insight anyone has, and am concerned this could happen to other people too.

Well, I bought myself another Nexus so I'd have something to keep me going. I also disassembled my faulty one to inspect the module with the 32GB Sandisk memory, but couldn't see anything wrong with it. If I can find a replacement, I can easily swap modules I suppose...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

What about the output of adb shell ls -l --color=never /system/bin? Maybe one of the necessary programs (e.g. mount) is missing or has a dead link.
-Snags

Snags697 said:
What about the output of adb shell ls -l --color=never /system/bin? Maybe one of the necessary programs (e.g. mount) is missing or has a dead link.
Click to expand...
Click to collapse
Thanks for the response, Snags. I uploaded output to that here...
http://ErichMoraga.com/color.txt
I haven't scoured that for yet for missing programs, dead links, etc. Mount seems to be there...
lrwxrwxrwx 1 0 0 19 Jul 5 2012 mount -> /system/bin/busybox
Since there's so much BusyBox redirection going on there, it still supports my theory that the BusyBox installation was the root cause of the read only memory issue.

I'm sure there is a way to debug the Nexus in real-time. I'll have to find out the command for that (ie. dump threads, etc. as they occur to my PC via USB). A reliable way to crash the phone is to wait about 5 seconds into the scan at... Settings > Storage

I also noticed other people have similar problems not being able to write any of their memory...
http://forum.xda-developers.com/showthread.php?t=1756111

I'm a Linux guy and just learning Android. My first impression would be to double-check with a known writable directory. If you can't write in the /data/local directory (adb push anyfile /data/local/), check the mount status of everything: adb shell toolbox mount should do that with the native toolbox instead of busybox. Each entry should list either "rw" or "ro" amidst the gibberish. If /data is "ro", remounting from a root prompt (toolbox mount -o remount,rw ... /data) (Note: no space before rw, and replace ... with whatever was listed before /data in the list of mounted filesystems above) may give you write access to /data/local.
Then again, I think this is pointless, because if fastboot can't write to the internal SD (like the link you posted), something hardware-related or partition-related must be going on. Maybe the partition table got fried. Fastboot is only willing to write whole partitions that are genuine, I think. So if the partitions are messed up, it may prevent fastboot from doing anything. To see the partition table, you'd need root (there's a hole in the bucket...) and from a root prompt, run: parted /dev/block/mmcblk0 then from the (parted) prompt, type print. Quit or exit should get you out of there. Compare the output to "Need a copy of a stock GSM Nexus partition table" (Google it, I can't post links yet).
Of course, if you don't have root, this all doesn't help.
-Snags

Well, Snags, let's just say great minds think alike :good:
Also, I have root, and bought another Nexus that should arrive this week to play with that I'll flash with a nandroid backup from a couple weeks ago. The mount output looked fine...
rootfs on / type rootfs (ro,noatime)
tmpfs on /dev type tmpfs (rw,nosuid,noatime,mode=755)
devpts on /dev/pts type devpts (rw,noatime,mode=600)
proc on /proc type proc (rw,noatime)
sysfs on /sys type sysfs (rw,noatime)
none on /acct type cgroup (rw,noatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,noatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,noatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,noatime,cpu)
/dev/block/platform/omap/omap_hsmmc.0/by-name/system on /system type ext4 (rw,noatime,barrier=1,data=ordered,noauto_da_alloc)
/dev/block/platform/omap/omap_hsmmc.0/by-name/userdata on /data type ext4 (rw,nosuid,nodev,noatime,errors=panic,barrier=0,nomblk_io_submit,data=ordered,noauto_da_alloc)
/dev/block/platform/omap/omap_hsmmc.0/by-name/cache on /cache type ext4 (rw,nosuid,nodev,noatime,errors=panic,barrier=0,nomblk_io_submit,data=ordered,noauto_da_alloc)
/dev/block/platform/omap/omap_hsmmc.0/by-name/efs on /factory type ext4 (ro,noatime,barrier=1,data=ordered,noauto_da_alloc)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,noatime)
/dev/block/platform/omap/omap_hsmmc.0/by-name/userdata on /mnt/sdcard type ext4 (rw,nosuid,nodev,noatime,errors=panic,barrier=0,nomblk_io_submit,data=ordered,noauto_da_alloc)
/sbin # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC SEM32G (sd/mmc)
Disk /dev/block/mmcblk0: 31.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 524kB 4194kB 3670kB sbl
3 4194kB 25.2MB 21.0MB ext4 efs
4 25.2MB 33.6MB 8389kB param
5 33.6MB 37.7MB 4194kB misc
6 37.7MB 41.9MB 4194kB dgs
7 41.9MB 50.3MB 8389kB boot
8 50.3MB 62.8MB 12.5MB recovery
13 62.8MB 62.9MB 65.5kB metadata
9 62.9MB 79.7MB 16.8MB radio
10 79.7MB 765MB 686MB ext4 system
11 765MB 1218MB 453MB ext4 cache
12 1218MB 31.9GB 30.7GB ext4 userdata
I've also included some other stuff...
</etc/fstab>
/dev/block/platform/omap/omap_hsmmc.0/by-name/cache /cache ext4 rw
/dev/block/platform/omap/omap_hsmmc.0/by-name/userdata /data ext4 rw
/dev/block/platform/omap/omap_hsmmc.0/by-name/system /system ext4 rw
</etc/recovery.fstab>
# mount point fstype device
# there is no actual sdcard in this thing...
#/sdcard vfat /dev/block/sda1
/system ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/system
/cache ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/cache
/data ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/userdata
/misc emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/misc
/boot emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/boot
/recovery emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/recovery
/sbl emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/sbl
/xloader emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/xloader
/radio emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/radio
Bear in mind I have a Verizon CDMA phone, so the partition table is different than GSM's (32GB vs. 16GB). Oddly enough, I couldn't locate the CDMA version online. Here is one of the the GSM versions I found...
Model: MMC VYL00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 524kB 4194kB 3670kB sbl
3 4194kB 25.2MB 21.0MB ext4 efs
4 25.2MB 33.6MB 8389kB param
5 33.6MB 37.7MB 4194kB misc
6 37.7MB 41.9MB 4194kB dgs
7 41.9MB 50.3MB 8389kB boot
8 50.3MB 62.8MB 12.5MB recovery
13 62.8MB 62.9MB 65.5kB metadata
9 62.9MB 79.7MB 16.8MB radio
10 79.7MB 765MB 686MB ext4 system
11 765MB 1218MB 453MB cache
12 1218MB 15.8GB 14.5GB userdata
The only differences were the specification of ext4 in mine under 11 & 12, as well as the size in 12. I also noticed Koush documented the recovery.fstab to have "auto" for /data instead of ext4 like mine. Worst case, I can run some comparisons between my 2 phones when the new one arrives. It won't be hard to push the correct changes if found.

Yet another person has the same problem as me... [writing to the memory card isn't actually committed, effectively making it read-only]
http://forum.xda-developers.com/showthread.php?p=28707474
My new phone will arrive Monday so I'll be able to perform more comparative analysis then. That said, since parted can't even make effective changes (I already tried), this may be a tricky fix.

If you don't mind the fact that it'll result in a full wipe including internal storage, you could try:
Open up any Google official ROM and extract the userdata img file.
Go into fastboot and flash that img. Reboot. Let it go through the full reboot process.
If something went wonky with how the partition is configured, that should set it straight. If it's a hardware problem you are still boned.

ErichMoraga said:
Yet another person has the same problem as me... [writing to the memory card isn't actually committed, effectively making it read-only]
http://forum.xda-developers.com/showthread.php?p=28707474
My new phone will arrive Monday so I'll be able to perform more comparative analysis then. That said, since parted can't even make effective changes (I already tried), this may be a tricky fix.
Click to expand...
Click to collapse
So yes, it seems i have a pretty similar problem with mine : nothing can be written anymore on the internal memory, whatever i can try : in recovery, in windows or with a file manager in the phone. Plus it is in bootloops constantly.
But i haven't touch at Busybox at all ; i mean it comes with Trinity kernel i use, so i don't bother to install or update it....Problem appeared just after this procedure :
- Downloaded a new Rom
- Rebooted to recoverry (TWRP)
- Made a Nand
- Wiped cache/dalvik/data
-Flashed new Rom/ gapps
-Rebooted...in the old configuration, just as if i've done nothing ! O_O......then i knew something was getting really bad....
As i said in the other thread (http://forum.xda-developers.com/showthread.php?t=1756334&page=2) i've just sent it to Samsung for repair under warranty...so i'll tell you in about 2/3 weeks when they'll return it, if they accept it, becaused even if I relocked the bootloader, it is still rooted.....but as it is surely a hardware problem, the warranty should work.
Anyway, i read somewhere that people had experienced this kind of issue after a "bad nandroid", or EMMC (?)....i'm not sure of what it means though....

Yeah, I'm leaning towards the hardware side too. It looks like the SANDISK NAND that Samsung used in the Nexus is a bit unstable. Also, I ran...
fastboot flash userdata userdata.img
sending 'userdata' (139193 KB)...
OKAY [ 15.448s]
writing 'userdata'...
OKAY [ 9.876s]
finished. total time: 25.325s
Not surprisingly the data was unchanged when I booted up. I might call Samsung later today to get the ball rolling.

ErichMoraga said:
Yeah, I'm leaning towards the hardware side too. It looks like the SANDISK NAND that Samsung used in the Nexus is a bit unstable. Also, I ran...
fastboot flash userdata userdata.img
sending 'userdata' (139193 KB)...
OKAY [ 15.448s]
writing 'userdata'...
OKAY [ 9.876s]
finished. total time: 25.325s
Not surprisingly the data was unchanged when I booted up. I might call Samsung later today to get the ball rolling.
Click to expand...
Click to collapse
Yeah, that's not surprising me...let's them repair their **** after all....

Samsung was pretty quick with the repair. There was a status update yesterday...
"The unit has left the technician. SOLUTION: Replaced Component - PRL Updated - S/W Updated - Passed"
I assume they replaced the module that holds the SIM slot and SANDISK chip. I'm sure I'll receive the phone soon, although I've been using a backup i515 I bought on eBay earlier.

[Q] Can't install apps (COS 4.0.4 and INT2EXT+)

I'm running COS ICS firmware with INT2EXT+ (from here). Everything seemed to be fine, but today I suddenly noticed that I can't neither install a new app nor update an already installed one. The download bar is blinking endlessly without getting anywhere.
As I can understand, the problem is that /data/data is full, but what can be done with it? I suppose that if I move it to the EXT partition, it will become even more sloppy than it is now.
Here's the output of df:
Code:
[email protected]:/ $ df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 207560 60 207500 0% /dev
tmpfs 207560 0 207560 0% /mnt/asec
tmpfs 207560 0 207560 0% /mnt/obb
/dev/block/mtdblock3 256000 178684 77316 70% /system
/dev/block/mtdblock4 40960 1288 39672 3% /cache
/dev/block/mmcblk0p2 1874298 277453 1496841 16% /data
/dev/block/mtdblock5 151168 147324 3844 97% /data/data
/dev/block/mtdblock5 151168 147324 3844 97% /data/property
/dev/block/mtdblock5 151168 147324 3844 97% /data/radio
/dev/block/vold/179:1
5756032 1851000 3905032 32% /mnt/sdcard
df: /mnt/secure/asec: Permission denied
/dev/block/dm-0 9352 7532 1820 81% /mnt/asec/com.readability-1
Any suggestions?
Thanks.

Try settings/ applications then find google play store and clear cache n data. Worked for me earlier
Sent from my HTC Desire

jmcclue said:
Try settings/ applications then find google play store and clear cache n data. Worked for me earlier
Sent from my HTC Desire
Click to expand...
Click to collapse
Thanks, but it doesn't seem to be the problem, as Play Store had some ~1 MB in cache and even less in data.
I uninstalled several relatively big apps (like Google+), which made /data/data only 71% full, so I could update other apps. But it's a temporary solution; is there really no way to get more space for apps on HTC Desire without making it slow and clumsy?

shlema said:
Thanks, but it doesn't seem to be the problem, as Play Store had some ~1 MB in cache and even less in data.
I uninstalled several relatively big apps (like Google+), which made /data/data only 71% full, so I could update other apps. But it's a temporary solution; is there really no way to get more space for apps on HTC Desire without making it slow and clumsy?
Click to expand...
Click to collapse
Yea...by getting a new phone with bigger memory. Sd-ext will always be slow.
Sent from my toaster

abaaaabbbb63 said:
Yea...by getting a new phone with bigger memory. Sd-ext will always be slow.
Sent from my toaster
Click to expand...
Click to collapse
Well... Then I'll go for dGB ROM for now, will see if 360 MB is enough for my apps. =)

CWM Touch v6.0.4.7

delete thread please!

great work thank you munjeni:good:

Great! Thanks, munjeni

Thanks! Works great but saved the backup has a date 1970.02.07 ... just like in the previous version. Maybe it is how to backup wrote in the current date?

Never had internal srorage emulated so our phone is my first phone which have emulated storage. Does anyone have idea where is block device for internal sdcard??? I thinking its (in) mmcblk0p25 ? More info about internal sdcard is welcome!

New version is out! http://forum.xda-developers.com/attachment.php?attachmentid=2594573&d=1393093417

1jkan said:
Thanks! Works great but saved the backup has a date 1970.02.07 ... just like in the previous version. Maybe it is how to backup wrote in the current date?
Click to expand...
Click to collapse
Tnx for feedback, I will use date and time from kernel (time which is displayed on main screen) for backup name... :good:

munjeni said:
Never had internal srorage emulated so our phone is my first phone which have emulated storage. Does anyone have idea where is block device for internal sdcard??? I thinking its (in) mmcblk0p25 ? More info about internal sdcard is welcome!
Click to expand...
Click to collapse
it's look like XZ1c uses unified storage.
unified storage = intenal storage(/mnt/sdcard0/) --> /data/media
Code:
[email protected]:/storage/sdcard0 # df
Filesystem Size Used Free Blksize
/dev 343.1M 72.0K 343.0M 4096
/mnt/asec 343.1M 0.0K 343.1M 4096
/mnt/obb 343.1M 0.0K 343.1M 4096
/system 1009.3M 877.7M 131.6M 4096
[COLOR="Red"]/data 3.9G 1.3G 2.6G 4096[/COLOR]
/cache 246.2M 4.3M 241.9M 4096
/data/idd 7.5M 1.1M 6.4M 1024
[COLOR="red"]/storage/sdcard0 3.9G 1.3G 2.6G 4096[/COLOR]
/mnt/asec/com.keramidas.TitaniumBackupPro-1 2.0M 80.0K 1.9M 4096
/mnt/asec/com.mobisystems.editor.office_registered-1 50.0M 48.7M 1.3M 4096
/mnt/asec/com.quoord.tapatalkHD-2 31.0M 29.2M 1.9M 4096
/storage/sdcard1 29.7G 27.8G 1.9G 32768
[email protected]:/storage/sdcard0 #
mounts :
Code:
[email protected]:/storage/sdcard0 # mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,noatime,nodiratime,mode=755 0 0
devpts /dev/pts devpts rw,noatime,nodiratime,mode=600 0 0
proc /proc proc rw,noatime,nodiratime 0 0
sysfs /sys sysfs rw,noatime,nodiratime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,noatime,nodiratime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,noatime,nodiratime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-num/p12 /system ext4 ro,relatime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-num/p14 /data ext4 rw,nosuid,nodev,noatime,nodiratime,nobarrier,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-num/p13 /cache ext4 rw,nosuid,nodev,noatime,nodiratime,nobarrier,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-num/p10 /data/idd ext4 rw,nosuid,nodev,noatime,nobarrier,data=ordered 0 0
[COLOR="Red"]/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,noexec,noatime,nodiratime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0[/COLOR]
/dev/block/dm-0 /mnt/asec/com.keramidas.TitaniumBackupPro-1 ext4 ro,nosuid,nodev,relatime 0 0
/dev/block/dm-1 /mnt/asec/com.mobisystems.editor.office_registered-1 ext4 ro,nosuid,nodev,relatime 0 0
/dev/block/dm-2 /mnt/asec/com.quoord.tapatalkHD-2 ext4 ro,nosuid,nodev,relatime 0 0
/dev/block/vold/179:33 /storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
from /system/build.prop
Code:
# It is changed to true in msm8660_surf
# Change it back to false according to blue
#
# Simulate sdcard on /data/media
#
[B][COLOR="Red"]persist.fuse_sdcard=false[/COLOR][/B]
this example i take from lt26w build.prop the value should be true for XZ1c.
/init.semc.rc
Code:
# msm specific files that need to be created on /data
on post-fs-data
# we will remap this as /mnt/sdcard with the sdcard fuse tool
mkdir /data/media 0775 media_rw media_rw
chown media_rw media_rw /data/media
mkdir /data/media/Download 0775 media_rw media_rw
chown media_rw media_rw /data/media/Download
/init.sony-device.rc
Code:
# User 2800: sdcardd
service sdcardd /system/bin/sdcard /mnt/int_storage 2800 2800
user root
group sdcard_rw
disabled
/system/bin/sdcard --> binary to fuse mount /data/media to /mnt/int_storage
i have managed to enable unified storage on lt26w by editing the build.prop and vold.fstab.hopefully this could help with internal storage mounts on XZ1c.

Do you have idea how we can mount them to loop device? I had no time to play with them but block device is reguired for mounting them to pc. Idea is to mount them somehow to loop device -> than mount loop to the an folder -> than echo loop device to lun file. I have no tried to mount them manualy using sdcard tool. Maybe better solution is repartitioning emmc and making vfat partition for internal sdcard since it will be easy for mounting (ramdisk will need modification).

munjeni said:
Do you have idea how we can mount them to loop device? I had no time to play with them but block device is reguired for mounting them to pc. Idea is to mount them somehow to loop device -> than mount loop to the an folder -> than echo loop device to lun file. I have no tried to mount them manualy using sdcard tool. Maybe better solution is repartitioning emmc and making vfat partition for internal sdcard since it will be easy for mounting (ramdisk will need modification).
Click to expand...
Click to collapse
http://teamw.in/DataMedia
Because the "internal sdcard" is not a true FAT file system, you can't mount it via USB storage. Well, that's not technically true, but the vast majority of people use Windows computers and Windows doesn't recognize ext4. If we were to allow you to mount the data partition via USB storage, Windows would claim that the device wasn't formatted and offer to format it for you, which, as you can imagine, would be a disaster. The whole ext4 setup is another reason that Android switched to using MTP for transferring files. Most of these devices don't have the necessary kernel configuration to even support USB storage mode, so it's not very easy to enable USB storage if we even wanted to try. Unfortunately at this time, MTP isn't available in recovery, so if you have no other option, you will have to use adb to push and pull files to/from your device.
Click to expand...
Click to collapse

Yes, you are right, thats not posible since partition is not fat, only in linux we can see mounted storage, but thats not what we want. Will remove internal sd in mount storage menu.

any other download link for the boot.img ? thanks

munjeni said:
Hi, here is my version of the recovery, almost full working.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What working what not working:
Working:
- everything including adb and external sdcard
Not working:
- can not mount internal sdcard, but I will try to get them working soon
New feature:
- increased brightness of the recovery
- battery level (icon!) in real time
- clock (icon!) in real time
- battery charging led indicator
Changelog 22.Feb.2014 :
- redesigned
- special menu (will make them soon!)
- new font (lucida console)
How to install:
1. for locked bootloaders only:
- Our recovery is replacement for not working Philz recovery from post -> http://forum.xda-developers.com/showthread.php?t=2647480
- download zip from these post (Z1C-lockeddualrecovery[VERSION]-BETA.installer.zip), download ramdisk-recovery.cpio.lzma -> http://munjeni.homeunix.com/ramdisk-recovery.cpio.lzma, rename ramdisk-recovery.cpio.lzma to recovery.philz.cpio.lzma, copy them to Z1C-lockeddualrecovery[VERSION]-BETA.installer.zip by replacing file recovery.philz.cpio.lzma in zip
2. for unlocked bootloaders only:
- download boot.img from http://munjeni.homeunix.com/z1c_boot.img , reboot to fastboot, flash boot.img with fastboot, go to http://forum.xda-developers.com/showthread.php?t=2620794 and give thanks to author of the ramdisk! Thanks man! My work is only on CWM, everything other is extracted from his boot image! Boot image contain CWM + stock rom ramdisk + stock rom kernel = for stock rom 14.2.A.1.114 only!
If something is not working please let me know! Enjoy!
Click to expand...
Click to collapse
Hi, the link under 1 for downloading /ramdisk-recovery.cpio.lzma is not working, server seems to be down

Server is up again, sorry

This CWM is great. I had some issues with the other (dual boot TWRP) and installing a ROM. I have installed a ROM and run backups. Haven't had time to test restore. Well done!

munjeni said:
Tnx for feedback, I will use date and time from kernel (time which is displayed on main screen) for backup name... :good:
Click to expand...
Click to collapse
Is there a way to change this to the normal date/timestamp?
This is confusing. See Screenshot from today.
In every backup, I have to rename the backup at least.
Regards, Chris
Sent from my Xperia Z1 Compact using XDA Premium HD mobile app.

dhchris said:
Is there a way to change this to the normal date/timestamp?
This is confusing. See Screenshot from today.
In every backup, I have to rename the backup at least.
Regards, Chris View attachment 2721115
Sent from my Xperia Z1 Compact using XDA Premium HD mobile app.
Click to expand...
Click to collapse
Thats a known isue on CWM recovery ! I don't think if these bug will be solved soon since recovery have no internet access to sinchronise time, so recovery can not know actual date! Maybe we can implement something for getting time from radio (not sure if it is possible).

If that's the reason, then where does TWRP get the correct date and time from because there it works?

Iruwen said:
If that's the reason, then where does TWRP get the correct date and time from because there it works?
Click to expand...
Click to collapse
Sorry I dont know, but I will look into twrp source code to get idea, have no free time for cwm, but maybe later.

dhchris said:
Is there a way to change this to the normal date/timestamp?
This is confusing. See Screenshot from today.
In every backup, I have to rename the backup at least.
Regards, Chris View attachment 2721115
Sent from my Xperia Z1 Compact using XDA Premium HD mobile app.
Click to expand...
Click to collapse
Excuse me for interfering...
This date format is to sort the backups. First is year, next month and last for day.
If you are using a "normal" datestamp, your files are not listed in sequence.
So, in this case your files are always listed in a way, that latest backup is the last in row.

[HINT] DiskUsage app, "System data" and the lost storage space

Hello everyone, I want to share my findings on the topic said in the thread title.
Someone used to visit this forum might think that the topic is been asked and answered already in the past but what I found is something that is not been said already, or, at least, is not that easy to find.
Owners of smartphone with very limited internal storage, like Galaxy Y, will likely end up to be concerned of every single MB of storage space that seems to be "lost"; and so that's why me too I start my search to find the reason and any possibile fix to get rid of a large "system data" block that was wasting about 7% of space in my 2nd SDcard partition.
Let's note this please: I'M NOT talking about the "system data" block shown in the primary (1st or only) partition on SDcard as shown by the Diskusage app.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
*THAT* "System data" block is just the space used by the .android_secure folder (that exist on root of SDcard in case some apps have been moved there) but not reported by Diskusage in the shown *virtual* App2SD folder.
The SDcard/.android_secure folder is mount as /mnt/secure/asec and there the size can be checked.
As you can see the size of .android_secure folder, in this example, is 179.60MB that is exactly the sum of App2SD folder and System data block (85.5+94.1=179.6).
But what is this?
Here you can see a "huge" 28.4MB "System data" block that eats more than 7% of the 2nd SDcard partition.
As many other Galaxy Y owners I've installed Link2SD app on my phone, that provides a convenient way to move davilk-cache apps files (eventually along with the data files in the Plus version) from internal storage Data partition to a secondary partition on the SDCard.
In my opinion Link2SD is the best solution for storage management... beside that Link2SD provide a lot of useful functionalities and informations, it is also not advisable to completely replace the small internal Data partition with a big partition that reside on the SDcard, because in the not so unlikely event of a SDcard failure the phone will be left in a completely unusable status; furthermore the internal storage sequential write and random performance might be much better than a cheap SDcard.
....
[/data partition performance test with AndroBench]...[/sdcard partition performance test]
With the help of Link2SD (and many other manual operations) I've been able to get an excellent 55% of free storage space in /Data partition while the phone is still fully functional in case of removal, missing, or failure of SDcard.
[User apps fully installed and running in internal storage(/system, /data, /cache): Browser, Youtube, Quickoffice, Maps, Google Play Store, Trillian, VoipCheapGlobal, Gmail, Mail, QuickPic, Tethering Widget, Flashlight, Root Explorer, Terminal Emulator, SSHDroid, VNC_server]
Unlike the "System data" block in SDcard, the one in 2nd partition is completely unrelated to any apps and, THERE'S NO WAY TO REMOVE IT BY DOING ANY FILE OR FOLDER REMOVAL.
What DiskUsage show as "System data" is actually "reserved blocks" that is pertinent to the design of Ext filesystems generation (Ext2/3/4), along with the blocks used for journaling (Ext3/4).
Those "reserved blocks" were thought as a "emergency room for root" to avoid the case of root user not able to login because of zero left free space in filesystem.
By deafult this reserved blocks amount is computed as 5% of filesystem size, and that might be a super huge waste of space (think of a 50GB reserved on a 1000GB filesystem) especially in the case of a "non system" partition, like the ones in SDcard (other infos here http://unix.stackexchange.com/questions/41125/ext2-3-4-reserved-blocks-percentage-purpose).
So, in order to free up the useless "reserved blocks", that's what I did on a Linux box equipped with a card reader (/dev/mmcblk0)
First I checked the amount of reserved blocks
Code:
[email protected]:/home/knoppix# tune2fs -l /dev/mmcblk0p2 | grep Reserved
Reserved block count: 21247
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
Then I've set the reserved blocks percentage to 0%
Code:
[email protected]:/home/knoppix# tune2fs -m 0 /dev/mmcblk0p2
tune2fs 1.42.5 (29-Jul-2012)
Setting reserved blocks percentage to 0% (0 blocks)
DONE!
While doing my research on this topic, I realized that my Ext3 filesystem I made long time ago, didn't fit the whole partition... so I had few extra MB wasted; to get them back that's what I did:
I first checked the partition size
Code:
[email protected]:/home/knoppix# fdisk -l | grep mmcblk0p2
/dev/mmcblk0p2 3037184 3887103 424960 83 Linux
mount the partition in /media/mmcblk0p2 and checked the filesystem size
Code:
[email protected]:/home/knoppix# df /media/mmcblk0p2
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mmcblk0p2 404378 295442 88052 78% /media/mmcblk0p2
UNMOUNT and perform a filesystem check (mandatory)
Code:
[email protected]:/home/knoppix# umount /dev/mmcblk0p2
[email protected]:/home/knoppix# e2fsck -f /dev/mmcblk0p2
e2fsck 1.42.5 (29-Jul-2012)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/mmcblk0p2: 2769/104448 files (24.8% non-contiguous), 308754/417690 blocks
resize the filesystem to partition size
Code:
[email protected]:/home/knoppix# resize2fs /dev/mmcblk0p2
resize2fs 1.42.5 (29-Jul-2012)
Resizing the filesystem on /dev/mmcblk0p2 to 424960 (1k) blocks.
The filesystem on /dev/mmcblk0p2 is now 424960 blocks long.
Mount again and check the new filesystem size:
Code:
[email protected]:/home/knoppix# df /media/mmcblk0p2
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mmcblk0p2 411387 295442 94698 76% /media/mmcblk0p2
And that's the final result!
"System data" shrinked from 28.4MB to only 8MB!
The left 8MB are in use for the filesystem journaling.
FAT and Ext2 filesystems doesn't make use of journaling so there's not reserved space for that.
Therefore in order to gain few others free MB is possible to use Ext2 in place of Ext3, given that Ext2 (according to a Wikipedia page here http://en.wikipedia.org/wiki/Ext2 ) "is still the filesystem of choice for flash-based storage media".
...