Goal:
Motivation: As my phone (Sony Ericsson SK17i) has low internal memory, it is essential to have a good MicroSD card with sd-ext and move some parts of /data to /sd-ext.
Problem: I am not satisfied with random I/O performance on ext4.
I, however, don't want to sacrify safety by disabling journaling.
My HW&SW:
My MicroSD: Samsung EVO MB-MP32D/EU, 32GB.
My phone: Sony Ericsson Xperia Mini Pro (SK17i)
ROM: LegacyXperia CM11
Ext4 mount options: noatime,nodiratime,barrier=1
My laptop OS (I ran mkfs.ext4, GParted and fdisk tools there): Ubuntu 12.04, up-to-date
Before making any change, I did a byte-by-byte backup of the original raw data, that is roughly dd if=/dev/sdc bytes=(some size) | compression > output_file. If you are interested in it, you can download the https://public.v6ak.com/samsung-evo-MB-MP32D--EU--32GB/sdc.gz.bz2 (< 1KiB) backup file.
What and why I did:
First, I resized the FAT32 (without reformatting) to 20GiB by GParted,
Second, I determined the sdcard characteristics by flashbench tool using command sudo ./flashbench -a /dev/sdc --blocksize=1024: https://public.v6ak.com/samsung-evo-MB-MP32D--EU--32GB/
There is my conclusion:
Code:
erase_block = 16777216
multi_plane = 16384
page = 8192
So, I took recommendation from https://wiki.gentoo.org/wiki/SDCard#Solution_2:_Tuned_ext4:
Code:
filesystem_block = min(page, 4096) = 4096 # Values higher than 4096 are not supported, so I had to pick 4096.
stride = multi_plane / page = 2 # Should I use page, or filesystem_block?
stripe_width = erase_block / page = 2048 # Should I use page, or filesystem_block?
# The resulting command:
sudo mkfs.ext4 -E stride=2,stripe-width=2048 -b 4096 /dev/sdc2
Third, I made another partitions in the free space. Now, I am just interested in the /dev/sdc2, which is sd-ext. The start of all the partitions is divisible by 8192, so I hope they are all properly aligned:
Code:
Disk /dev/sdc: 32.0 GB, 32010928128 bytes
255 heads, 63 sectors/track, 3891 cylinders, total 62521344 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0000cf13
Device Boot Start End Blocks Id System
/dev/sdc1 8192 41951231 20971520 c W95 FAT32 (LBA) # The original partition
/dev/sdc2 41951232 50339839 4194304 83 Linux # The sd-ext partition
/dev/sdc3 50339840 52436991 1048576 83 Linux # A legacy partition, nothing important
/dev/sdc4 52436992 56631295 2097152 b W95 FAT32 # Titanium Backup partition, not important at the moment
The results:
I used A1 SD Bench to benchmark both FAT32 (i.e. /dev/sdc1) and ext4 (i.e. /dev/sdc2) filesystems. I did just the random I/O test when phone was in airplane mode (=> no noise from network events) and charging:
{
"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"
}
I've seen some suggestions it should perform several times better: http://forums.storagereview.com/index.php/topic/36678-samsung-evo-sd-memory-card-review-discussion/?p=287587 (Well, SD and microSD might differ, but I hope it not to differ much.)
There are my questions:
* Why is random write performance on the original FS significantly lower than on the benchmark above?
* Random writes are about twice faster on FAT32 than on ext4. Is it caused just by journaling?
* Why is random read significantly better on FAT32 than on ext4?
* Did I choose the right stripe/stride/blocksize? Should I double them?
* Should I perform another benchmark?
P.S.: Sorry there are no hyperlinks, I am not allowed to post them. I've tried to make the references as friendly as possible.
Related
Do any of you have any suggestions on how to do this? I ran parted via ADB on my 8GB tablet's internal storage (/dev/block/mmcblk0)
Code:
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 25.2MB 21.0MB ext4 EFS
2 25.2MB 27.3MB 2097kB SBL1
3 27.3MB 29.4MB 2097kB SBL2
4 29.4MB 37.7MB 8389kB PARAM
5 37.7MB 46.1MB 8389kB KERNEL
6 46.1MB 54.5MB 8389kB RECOVERY
7 54.5MB 789MB 734MB ext4 CACHE
8 789MB 810MB 21.0MB MODEM
9 810MB 2278MB 1468MB ext4 FACTORYFS
10 2278MB 7281MB 5004MB ext4 DATAFS
11 7281MB 7818MB 537MB ext4 HIDDEN
I knew more or less what each partition did but was curious about "HIDDEN" so I mounted it to see what was there. All that was in that partition is Retail.apk (its the "Demo Mode" that runs when the tablet is sitting at Best Buy) and the sample multimedia files used in the demo. In total these files were less than 100MB and the multimedia already copied on the /sdcard/Samsung directory in the main storage.
537MB is quite significant considering how littte space there is on this 8GB model? The next time I do a factory reset can I just delete "HIDDEN" and DATAFS and create a new larger DATAFS partition with no ill effects? I'm thinking this would work because they are contiguous and enlarging DATAFS would not change its partition number so the mounting scripts during the boot process wouldn't get thrown off.
Are there any other suggestions on how I could reclaim 537 MB of internal storage?
I've done it successfully. delete p9,p10,p11 and recreate them in new size.
parted can only create ext2 partition, need tune2fs and e2fsck to convert ext2 to ext4 fs.
first, use tar to backup the system and data partition(p9,p10) to external_sd,
after repartition can restore them.
If you want to do it, must be careful, it's VERY DANGEROUS, maybe brick your device.
my device:Samsung Galaxy Tab2 P3110, CM 10.1.3RC2
{
"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"
}
For more detail you can have a look of this, it's in chinese and for kindle fire, but i think the commandline code you can understand.
http://bbs.imp3.net/thread-10515210-1-1.html
Have you succeeded in using all memory? I repartitioned device, in clockworkmod everything is fine, but I can't access all the space from system. For DATAFS I have now 5480MB instead of 5004MB, but system says me, that internal storage is still ~5GB with only 4,5GB available. I even hard resetted device - nothing changed. How to make system see all space?
it seems that all the memory of DATAFS are ok for my p3110, have a look of the snapshots below.
i use cm 10.1.3, i dont know which rom do you flash, stock rom?
sorry it is in chinese, but you could see the numbers of memory.
No problem with language, everything is clear . I'm using stock odexed Samsung 4.1.2 rom with my own changes for tabletui and a couple of others (like editing systemui.apk). I guess, that Samsung gives fixed amount of space for /data and I haven't found where it is. Anyway, thank you for idea
probably obvious to most, but don't delete all those partitions! i was in the middle of surgery via adb, and stupidly typed
Code:
du -hs
and the device rebooted.
http://forum.xda-developers.com/galaxy-tab-2/help/argh-deleted-internal-partitions-boot-t2912866
Hi people, i want to resize the internal partition of my P3100.
Can anyone help me?
First of all I decided to put all the memory available in user app (is /data?) so I can install more app, after this I need to know ho to resize /system partition and how much space I can take (I think 500MB is perfect)
After I need to enlarge my user app partitions without lost all my app and data app
Filesystem Size Used Free Blksize
/dev 345M 48K 345M 4096
/mnt/asec 345M 0K 345M 4096
/mnt/obb 345M 0K 345M 4096
/system 1G 363M 1014M 4096
/data 4G 3G 1G 4096
/cache 688M 11M 677M 4096
/efs 19M 8M 11M 4096
/storage/sdcard0 4G 3G 1G 4096
/storage/sdcard1 29G 10G 19G 32768
P.s.: what is it /mnt/asec and mntt/obb?
Can anyone make a short info about all the filesystem?
Aliendex said:
Hi people, i want to resize the internal partition of my P3100.
Can anyone help me?
First of all I decided to put all the memory available in user app (is /data?) so I can install more app, after this I need to know ho to resize /system partition and how much space I can take (I think 500MB is perfect)
After I need to enlarge my user app partitions without lost all my app and data app
P.s.: what is it /mnt/asec and mntt/obb?
Can anyone make a short info about all the filesystem?
Click to expand...
Click to collapse
I just want my girlfriend to be in the mood tonight. I think I have a better chance of that.
DigitalMD said:
I just want my girlfriend to be in the mood tonight. I think I have a better chance of that.
Click to expand...
Click to collapse
Very helpfull
Does this guide works?
[HOW-TO] Easily resize system + data partition!
The situation after 2 months is this:
System storage: 342MB used of 1024MB
Internal storage: 1.8GB used of 4.6GB
If i resize the system partition I can have a total of 5.1GB / 5.3GB for user apps
:cyclops:
{
"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"
}
Update: As a temporary solution I replaced the boot.img from 9/26 nightly with the one from 9/19 and have it working for now.
I can install the official release fine, and even CM nightly of Sept 19, (maybe 20 too, I didn't test). But if I try any nightly higher than that, it shows it installed fine, then I see the 1+ boot logo, then a bunch of strange color vertical lines and boot logo fades out, then reboot over and over. This even happens when installing custom roms from dev section if it's based on a build higher than 9/19.
I've done a full system and data wipe, installed official build, then tried to install latest nightly, but same error. Is there a way to check a log to see what's going on? The only thing I can think of is a while back I installed colorOS & miui to test them out. Maybe it affected partitions? I have no idea.
Thanks :good:
Here is what it looks like when I try to dirty flash latest nightly on top of stock CM11S:
{
"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"
}
Here is what it looks like when the install is "successful" of latest CM nightly after I wipe:
And here is a video showing what happens when I install something higher than 9/19 CM or any rom based off of higher:
https://www.youtube.com/watch?v=YVPkmEi3PGE
Thanks
Update your TWRP to 2.8.0.1
I updated and tried. It didn't show any errors on install but the same boot loop happens
Factory wipe and then re flash the rom gapps kernels etc
I did fastboot flash all of the original 11S files and it boots fine. Attempt at latest nightly, and bootloop. I found out how to copy the log, maybe this will help.
Also, according to the colorOS rom thread, when I flashed back to CM I did not get static_nvbk.bin & reserve4.img. Maybe this could be the issue? unfortunately I didn't back these up.
Here is the log:
Code:
I:Set page: 'flash_zip'
Installing '/sdcard/cm9-25nightly.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: Device or resource busy
about to run program [/tmp/backuptool.sh] with 2 args
grep: /tmp/gapps.prop: No such file or directory
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: Device or resource busy
about to run program [/tmp/otasigcheck.sh] with 1 args
Creating filesystem with parameters:
Size: 1388314624
Block size: 4096
Blocks per group: 32768
Inodes per group: 7712
Inode size: 256
Journal blocks: 5296
Label:
Blocks: 338944
Block groups: 11
Reserved block group size: 87
Created filesystem with 11/84832 inodes and 11157/338944 blocks
warning: wipe_block_device: Wipe via secure discard failed, used discard instead
minzip: Extracted 2 file(s)
minzip: Extracted 1525 file(s)
symlink(): created [/system/etc/firmware/wcd9320]
about to run program [/tmp/backuptool.sh] with 2 args
Writing radio image...
about to run program [/sbin/dd] with 3 args
2048+0 records in
2048+0 records out
1048576 bytes (1.0MB) copied, 0.046166 seconds, 21.7MB/s
about to run program [/sbin/dd] with 3 args
1000+0 records in
1000+0 records out
512000 bytes (500.0KB) copied, 0.018902 seconds, 25.8MB/s
about to run program [/sbin/dd] with 3 args
32768+0 records in
32768+0 records out
16777216 bytes (16.0MB) copied, 0.496146 seconds, 32.2MB/s
about to run program [/sbin/dd] with 3 args
64+0 records in
64+0 records out
32768 bytes (32.0KB) copied, 0.001728 seconds, 18.1MB/s
about to run program [/sbin/dd] with 3 args
1000+0 records in
1000+0 records out
512000 bytes (500.0KB) copied, 0.020736 seconds, 23.5MB/s
about to run program [/sbin/dd] with 3 args
131072+0 records in
131072+0 records out
67108864 bytes (64.0MB) copied, 2.224255 seconds, 28.8MB/s
about to run program [/sbin/dd] with 3 args
1024+0 records in
1024+0 records out
524288 bytes (512.0KB) copied, 0.023172 seconds, 21.6MB/s
script succeeded: result was [1]I:Legacy property environment disabled.
Updating partition details...
I:mount '/data/media/0' '/sdcard' process ended
On Sept 21 the CM nightlies made a change of "input: touchscreen: Update TP firmware to 14001219" I believe this is what's causing my bootloop problem. If this is the case, is it a hardware issue?
Well, I have some problems trying to crossflash modem.
I had some problems before, I managed to repair it with qpst, but now I cannot send my backup.
Where I am?
I have a qpst backup, and backup of modem, modemst1 and modemst2.
But when I try to dump it again over it do nothing.
Can someone give me a hand?
I have all phone working exept of movile data of course.
can someone tell me how to restore that partitions from download mode?
the seek and count?
Its an H950 with h950PR firmware
Thanks so much
{
"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"
}
well, I have some tests from adb and I cannot understand seek and count commands, so I try some but with no succes from ADB.
when I try to overwrite the partitions the log tell me that
Code:
[email protected]:/ # cd /data/media/0/
[email protected]:/data/media/0 # dd if=mod
modem.img modemst1.img modemst2.img
[email protected]:/data/media/0 # dd if=modem.img skip=1 of=/dev/block/mmcblk0p1
dd: /dev/block/mmcblk0p1: No space left on device
163841+0 records in
163840+0 records out
83886080 bytes transferred in 11.118 secs (7545069 bytes/sec)
1|[email protected]:/data/media/0 # dd if=modem.img bs=512 skip=1 of=/dev/block/mmcblk0p>
dd: /dev/block/mmcblk0p1: No space left on device
163841+0 records in
163840+0 records out
83886080 bytes transferred in 13.969 secs (6005159 bytes/sec)
d if=modemst1.img bs=512 skip=1 of=/dev/block/mmcblk0p23 <
dd: /dev/block/mmcblk0p23: No space left on device
3073+0 records in
3072+0 records out
1572864 bytes transferred in 0.294 secs (5349877 bytes/sec)
1|[email protected]:/data/media/0 # dd if=modemst2.img bs=512 skip=1 of=/dev/block/mmcbl>
dd: /dev/block/mmcblk0p24: No space left on device
3073+0 records in
3072+0 records out
1572864 bytes transferred in 0.179 secs (8786949 bytes/sec)
all backup are 1 record bigger than partitions.
I try with bs=512 skip=1 to avoid it, but without that I have the same problem...
can someone help me?
I can help!
first, use parted, and copy output of this:
./parted /dev/block/mmcblk0 unit s print
If the partition map is same with the H955, you cab backup with this commands:
the full backup of modemst1 and modemst2 size is: 1572864 byte
In download mode, copy backup files to internal storage:
dd if=/data/media/0/modemst1_mmcblk0p23.img of=/dev/block/mmcblk0 bs=8192 seek=20480 count=192
dd if=/data/media/0/modemst2_mmcblk0p24.img of=/dev/block/mmcblk0 bs=8192 seek=20672 count=192
In normal mode, booted android:
dd if=/data/media/0/modemst1_mmcblk0p23.img of=/dev/block/mmcblk0p23
dd if=/data/media/0/modemst2_mmcblk0p24.img of=/dev/block/mmcblk0p24
stars2 said:
I can help!
first, use parted, and copy output of this:
./parted /dev/block/mmcblk0 unit s print
If the partition map is same with the H955, you cab backup with this commands:
the full backup of modemst1 and modemst2 size is: 1572864 byte
In download mode, copy backup files to internal storage:
dd if=/data/media/0/modemst1_mmcblk0p23.img of=/dev/block/mmcblk0 bs=8192 seek=20480 count=192
dd if=/data/media/0/modemst2_mmcblk0p24.img of=/dev/block/mmcblk0 bs=8192 seek=20672 count=192
In normal mode, booted android:
dd if=/data/media/0/modemst1_mmcblk0p23.img of=/dev/block/mmcblk0p23
dd if=/data/media/0/modemst2_mmcblk0p24.img of=/dev/block/mmcblk0p24
Click to expand...
Click to collapse
Hi sr, Thanks for your answer.
The question is the next.
How to calculate seek and count, I understand that count*bs = size of partition, but seek is the blocks skipped, I dont understand how to know, Im on H950, partition table is the same, but sizes arent....
thanks so much
well, I dont know what happends, but my diag mode is useless.
I think my problem was overwritting the first 3 or 4 partitions.
can someone upload me a dump of first I think 100mb of a pr rom?
if was a full rom till system will be awesome.
a h955/950/950PR will work too for me.... I prefer to avoid antirollback roms...
thanks for the help
Your phone is even bootable?
Download parted binary, and execute this: /parted /dev/block/mmcblk0 unit s print
This is the example, how calculate seek and count
Number Start End Size File system Name
23 327680s 330751s 3072s modemst1
1. Calculate SKIP/SEEK
327680 sector * 512 byte (sector size) = 167772160 byte / 8192 (block size in byte) = 20480
2. Calculate Count (By the Partition size in sector)
You can use, the partition size in sector, or end sector - start sector
3072 sector * 512 byte (sector size) = 1572864 byte / 8192 (block size in byte) = 192
stars2 said:
Your phone is even bootable?
Download parted binary, and execute this: /parted /dev/block/mmcblk0 unit s print
This is the example, how calculate seek and count
Number Start End Size File system Name
23 327680s 330751s 3072s modemst1
1. Calculate SKIP/SEEK
327680 sector * 512 byte (sector size) = 167772160 byte / 8192 (block size in byte) = 20480
2. Calculate Count (By the Partition size in sector)
You can use, the partition size in sector, or end sector - start sector
3072 sector * 512 byte (sector size) = 1572864 byte / 8192 (block size in byte) = 192
Click to expand...
Click to collapse
yes sr, my phone is normally booting...
Ill try in a while and comment here.
thanks for the tips!
pelelademadera said:
yes sr, my phone is normally booting...
Ill try in a while and comment here.
thanks for the tips!
Click to expand...
Click to collapse
well, nothing, my phone works as a tablet...
I cannot restore my imei, all nv items are 000000, when phone is in diag mode I cannot send SPC.
which partition contains NV data?
I dont know how I broke it, I only overwrite modem.img with ATT one.
Do you think that booting with this partition makes that my phone will only work with att rom?
thanks so much for your time and explanation.
The bigger problem is that If I try with att rom, I have no way back
The modemst1 and modemst2 partition contain your imei and all nv data, these partitions is unique.
If this partitions damaged, deleted, your imei is lost and you can't restore, without a working backup...
stars2 said:
The modemst1 and modemst2 partition contain your imei and all nv data, these partitions is unique.
If this partitions damaged, deleted, your imei is lost and you can't restore, without a working backup...
Click to expand...
Click to collapse
Solved my problem sr.
phone is back...
So, I managed to wipe my filesystem when trying to root (going by the board that happens way too often I noticed).
I posted about it here https://forum.xda-developers.com/showpost.php?p=80579913&postcount=295 first.
But despite the quick and nice suggestions it still won't work.
Going by https://forum.xda-developers.com/showthread.php?t=3984875 I also tried to flash boot.img for Fastboot.
Yes, it's the right model ( GM21BA ) for Europe/Global 12gb/256
From make_f2fs.exe I get the following:
PS C:\temp> .\make_f2fs.exe [SERIAL]
F2FS-tools: mkfs.f2fs Ver: 1.9.0 (2017-11-13)
Info: Disable heap-based policy
Info: Debug level = 0
Info: Label =
Info: Trim is enabled
Error: Failed to get device size!
Click to expand...
Click to collapse
Which has me thinking the filesystem is gone.
And then I erased and formated boot twice, and am still left with RAW fs.
PS C:\temp> fastboot format:ext4 boot
Warning: boot type is raw, but ext4 was requested for formating.
Creating filesystem with parameters:
Size: 100663296
Block size: 4096
Blocks per group: 32768
Inodes per group: 6144
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 24576
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/6144 inodes and 1422/24576 blocks
target reported max download size of 805306368 bytes
sending 'boot' (5688 KB)...
OKAY [ 0.021s]
writing 'boot'...
OKAY [ 0.107s]
finished. total time: 0.130s
Click to expand...
Click to collapse
And then I tried F2FS with Fastboot Format:
PS C:\temp> fastboot format:f2fs boot
Warning: boot type is raw, but f2fs was requested for formating.
Formatting is not supported for filesystem with type 'f2fs'.
Click to expand...
Click to collapse
So, as I'm writing this I'm reading up on make_f2fs to have it format a new 'boot' for me to flash unto.
Well, at least I have fastboot even if I can't seem to manage flashing anything, so it could be lot worse...
User MSM tool to restore to factory default. It will ease everything, but you will have a working phone. Follow the directions on the thread located here.
For future reference, I'll write how I did manage to fix this:
I had tried using MSM earlier, but couldn't get the qualcom-drivers installed (as mentioned in the thread linked).
So, I tried having the tool already active (and certificates installed) as I pressed both volume up & down and plugged in the phone.
Now a port reacted and I could (with great excitment and haste) press install:
{
"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"
}
As expected it's back to stock.