Notices


Reply
Thread Tools
Posts: 46 | Thanked: 105 times | Joined on Sep 2017
#1971
Originally Posted by Heik View Post
Originally you created the file com.android.vending-1.apk using that touch command. So I guess you will get error message, if you run that command again, since it is locked by chattr +i command.

So, no need to rerun that.
Touch won't error it will just update the date and time the file was modified to 'now'
 

The Following 2 Users Say Thank You to suicidal_orange For This Useful Post:
Posts: 359 | Thanked: 644 times | Joined on Aug 2014
#1972
Originally Posted by n950 View Post
Hi,

I have installed Sailfish X 2.1.3.5 official on my F5121 xperia x 32 GB.

I have only 17,9 GB why?

How to fix it?
This process worked for ExplIT upon F5121:https://together.jolla.com/question/...post-id-156670

More detail from lantern for use on F5122 here:http://talk.maemo.org/showpost.php?p...postcount=1580

Last edited by aspergerguy; Today at 12:59. Reason: Addition
 

The Following 3 Users Say Thank You to aspergerguy For This Useful Post:
Posts: 57 | Thanked: 150 times | Joined on Jan 2012
#1973
Originally Posted by suicidal_orange View Post
Touch won't error it will just update the date and time the file was modified to 'now'
Is it so in the asa's case, as he has already used chattr +i to "lock" the file?
Code:
[nemo@Sailfish ~]$ touch /opt/alien/data/app/com.android.vending-1.apk
touch: cannot touch `/opt/alien/data/app/com.android.vending-1.apk': Permission denied
[nemo@Sailfish ~]$ devel-su
Password:
[root@Sailfish nemo]# touch /opt/alien/data/app/com.android.vending-1.apk
touch: cannot touch `/opt/alien/data/app/com.android.vending-1.apk': Permission denied
[root@Sailfish nemo]#
 

The Following User Says Thank You to Heik For This Useful Post:
Community Council | Posts: 4,120 | Thanked: 9,902 times | Joined on May 2012 @ Southerrn Finland
#1974
One thing I forgot to mention which happened to me and might be affecting other people too when flashing the XperiaX device;

There was no way I could make the device start in fastboot mode, nope, whether holding volume-UP or volume-DOWN or whichever combination of any of the buttons whatever!
I got the device to start up with the green LED light up but it was not recognized by fastboot!

What I could do, however was to boot it up normally, and then do "adb reboot-bootloader" which puts it correctly into fasboot mode.

Go figure.
 

The Following 5 Users Say Thank You to juiceme For This Useful Post:
Posts: 79 | Thanked: 354 times | Joined on Mar 2010 @ southern Italy
#1975
Originally Posted by n950 View Post
Hi,
I have only 17,9 GB why?
In the Sony Xperia X the advertised "32 Gb" are actually 29.1 Gb (31.2 billion bytes). And they have the usual baroque Android partitioning scheme (52 partitions, ouch!)

Thus we have:
- 20.7 Gb user partition (root+home, managed by lvm mapper)
- 7.3 Gb factory reset image
- ~1.1 Gb of supplementary partitions that must survive reformatting or even the factory reset (odm Sony drivers, FCC compliance HTML files, bluetooth associations, Android crash monitor, etc: sounds like everytime an Android system developer had some idea, he added a new partition for it).

So we have about 2.5 Gb for sailfish-root and the remaining 18.3 Gb for sailfish-home, as of the "sailfish" volume group of the lvm (logical volume manager).

In the last Mer/Sailfish meeting a few days ago they discussed the issue (see point 5) but maybe they'll have to strictly stick with Android partitioning because they're not authorized to do anything flashy.

I see the 7.3 Gb "factory reset" partition only contains ~600 megabytes (in the meeting they say "1.5Gb actually used by SailfishX", but AFAIK that's the uncompressed size; also, you could save 100 megabytes if you don't include the Sailfish_OS_2.0.mp4 file).

I guess we can reclaim about 6.6 Gb of those 7.3 Gb.

For example:
- backup factory reset partition data (~600 Mb ext4) into home
- fdisk: erase factory reset partition /dev/mmcblk0p52 (releasing those 7.3 Gb)
- fdisk: enlarge user partition (mmcblk0p51) from 20.7 Gb to 27.3 Gb (+6.6Gb), for example startsector=2334720 (same as before, doublecheck it) and endsector=59629567
- fdisk: create again /dev/mmcblk0p52 on the remaining ~700 Mb, for example startsector=59629568, endsector=61063167 (same as before)
- format the 700 Mb to ext4 and then restore its contents (SailfishX *img.gz images etc)
- restart the phone in recovery mode
- you now have 27.3 Gb (instead of 20.7) in mmcblk0p51 available to lvm, and the already filled 0.7 Gb in mmcblk0p52
- if the "vgdisplay" command does not show any Free PE blocks, then maybe you should "vgextend sailfish /dev/mmcblk0p51"
- now you should be able to manage the root/home volumes with lvm as suggested by seiichiro but enjoying the 27+Gb.

Even if the Sailfish "factory reset" required 1.5Gb instead of 0.6Gb, it would still be a +5.6Gb gain over the default partitioning scheme.

Disclaimer: I did not try to do it. Also, I'm no expert and I don't take responsibility. There's a chance some residual Android turd lying around could expect the partitioning scheme to not to change (maybe in the boot phase or even in the kernel): you may brick your Xperia soon after having rendered useless the Recovery Mode and the Factory Reset...
__________________
 

The Following 8 Users Say Thank You to alfmar For This Useful Post:
mrsellout's Avatar
Posts: 824 | Thanked: 1,851 times | Joined on Sep 2010 @ Manchester
#1976
Before even considering repartitioning it's worth reading the actual log [1] to become aware of the implications of deleting the wrong partition
eg
08:48:01 <abranson> really important areas. there are qualcomm partitions there that cannot be easily replaced, and permanently disable hardware or the entire phone if you mess with them
Then IF he still feel it's worth the effort, you'll know why you need to double and triple check (if not more) the commands before you execute.


[1] http://merproject.org/meetings/mer-m...log.html#l-175
 

The Following 2 Users Say Thank You to mrsellout For This Useful Post:
Posts: 1,388 | Thanked: 6,346 times | Joined on Apr 2010 @ Czech Republic
#1977
If only Android itself used LVM - it could just have one big volume group with whatever crazy logical volumes in it and we would not have these issues. LV order doesn't really matter, so you can easily remove LVs you don't need and create new ones using the recovered space.

There is really no good excuse for them as LVM has been there for ages and has basically been made to handle stuff like this in a much more robust way.

And this all is just using "normal" LVs - using a thin pool with thin LVs can be even more efficient & powerful.
__________________
modRana: a flexible GPS navigation system
Mieru: a flexible manga and comic book reader

Thanks to everyone who voted for modRana & Mieru in the Maemo.org coding competition !
 

The Following User Says Thank You to MartinK For This Useful Post:
Reply

Tags
sailfish os, sony xperia x

Thread Tools

 
Forum Jump


All times are GMT. The time now is 20:50.