|
[-]
[+]
|
Changed |
_service:tar_git:droid-config-j8210.changes
|
|
|
|
[-]
[+]
|
Changed |
_service:tar_git:droid-config-j8210.spec
^
|
|
|
|
|
Changed |
_service
^
|
|
[-]
[+]
|
Deleted |
_service:tar_git:droid-config-j8210-0.1.30.tar.bz2/sparse/etc/mce/60-memnotify-seine.conf
^
|
| @@ -1,2 +0,0 @@
-/system/osso/dsm/memnotify/warning/used=1032000
-/system/osso/dsm/memnotify/critical/used=1079000
|
|
[-]
[+]
|
Changed |
_service:tar_git:droid-config-j8210-0.1.31.tar.bz2/delete_file_j8210.list
^
|
| (renamed from delete_fil_j8210.list)
|
|
[-]
[+]
|
Changed |
_service:tar_git:droid-config-j8210-0.1.31.tar.bz2/kickstart/pack/j9110/hybris
^
|
| @@ -20,13 +20,6 @@
RELEASENAME=${NAME// /_}-${SAILFISH_CUSTOMER// /_}${SAILFISH_CUSTOMER:+-}${EXTRA_NAME// /_}$RND_FLAVOUR${RND_FLAVOUR:+-}$VERSION_ID$DEVICE_ID
-# Remove /opt mounting from fstab, systemd will handle it
-mkdir root
-mount -o loop root.img root
-sed -i '/\/opt/d' root/etc/fstab
-umount root
-rm -rf root
-
IMGSECTORS=0
IMGBLOCKS=0
IMGSIZE=0
@@ -100,36 +93,7 @@
/usr/sbin/vgchange -a n sailfish
-pigz -7 root.img && md5sum -b root.img.gz > root.img.gz.md5&
-pigz -7 home.img && md5sum -b home.img.gz > home.img.gz.md5&
-wait
-
-ROOTSIZE=$(/bin/ls -l root.img.gz | cut -d ' ' -f5)
-HOMESIZE=$(/bin/ls -l home.img.gz | cut -d ' ' -f5)
-
-# Temporary dir for making factory image backups.
-FIMAGE_TEMP=$(mktemp -d -p $(pwd))
-
-# For some reason loop files created by imager don't shrink properly when
-# running resize2fs -M on them. Hence manually growing the loop file here
-# to make the shrinking work once we have the image populated.
-dd if=/dev/zero bs=512 seek=$(/usr/bin/expr \( $ROOTSIZE + $HOMESIZE + 100000000 \) / 512) count=1 of=fimage.img
-/sbin/e2fsck -f -y fimage.img
-/sbin/resize2fs -f fimage.img
-
-mount -o loop fimage.img $FIMAGE_TEMP
-mkdir -p $FIMAGE_TEMP/${RELEASENAME}
-mv root.img.gz* $FIMAGE_TEMP/${RELEASENAME}
-mv home.img.gz* $FIMAGE_TEMP/${RELEASENAME}
-umount $FIMAGE_TEMP
-rmdir $FIMAGE_TEMP
-
-/sbin/e2fsck -f -y fimage.img
-/sbin/resize2fs -f -M fimage.img
-
-# To make the file magic right lets convert to single file sparse image.
-/usr/bin/img2simg fimage.img fimage.img001
-rm fimage.img
+rm home.img root.img
/sbin/losetup -d $LVM_LOOP
@@ -140,10 +104,6 @@
/usr/bin/img2simg sailfish.img sailfish.img001
rm sailfish.img
-# To make the file magic right lets convert to single file sparse image.
-/usr/bin/img2simg vendor.img vendor.img001
-rm vendor.img
-
chmod 755 flash.*
FILES="flash* *.img* *.exe *.dll *-release"
|
|
[-]
[+]
|
Changed |
_service:tar_git:droid-config-j8210-0.1.31.tar.bz2/sparse/boot/flash-on-windows.bat
^
|
| @@ -120,7 +120,7 @@
setlocal EnableDelayedExpansion
:: Find the blob image. Make sure there's only one.
-for /r %%f in (*_v12b_seine.img) do (
+for /r %%f in (*_v12a_kumano.img) do (
if not defined blobfilename (
REM Take only the filename and strip out the path which otherwise is there.
REM This is to make sure that we do not face issues later with e.g. spaces in the path etc.
|
|
[-]
[+]
|
Changed |
_service:tar_git:droid-config-j8210-0.1.31.tar.bz2/sparse/boot/flashing-README.txt
^
|
| @@ -1,17 +1,17 @@
-= SAILFISH X FOR SONY XPERIA™ 10 II FLASHING GUIDE =
+= SAILFISH X FOR SONY XPERIA™ 1/5 FLASHING GUIDE =
= FOR LINUX, WINDOWS AND OS X =
-= STEP 1: GETTING AN XPERIA™ 10 II =
+= STEP 1: GETTING AN XPERIA™ 1/5 =
-Get an Xperia™ 10 II. To be able to replace the Sony Android
+Get an Xperia™ 1/5. To be able to replace the Sony Android
system with Sailfish X, you will need to be able to unlock the bootloader of
your device so that it can be flashed with a new operating system. This process
is supported by Sony as part of their Open Devices programme:
https://developer.sony.com/develop/open-devices/
-The best way to get an unlockable device is to buy is a brand new Xperia™ 10 II
+The best way to get an unlockable device is to buy is a brand new Xperia™ 1/5
in a sales box. If you are tempted to buy second-hand please be aware that there
are some variants for which the bootloader cannot be unlocked: for example
devices that have at some point been SIM locked, even if they have subsequently
@@ -36,7 +36,7 @@
before you continue.
Go to https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/
-website and select the model of your device Xperia™ 10 II.
+website and select the model of your device Xperia™ 1/5.
You should see additional instructions to prepare your device for unlocking:
* Type the IMEI, accept the terms & conditions and press submit.
|
|
[-]
[+]
|
Added |
_service:tar_git:droid-config-j8210-0.1.31.tar.bz2/sparse/etc/mce/60-memnotify-kumano.conf
^
|
| @@ -0,0 +1,2 @@
+/system/osso/dsm/memnotify/warning/used=1471488
+/system/osso/dsm/memnotify/critical/used=1538560
|
