Reply
Thread Tools
Posts: 1,414 | Thanked: 7,547 times | Joined on Aug 2016 @ Estonia
#61
Originally Posted by pagis View Post
I will be joining the Tama (XZ3 single sim) club soon, please let me know if there are any hints or updates for the existing installation instructions, any chance to save TA?
I am preparing new set of images for flashing that will have

- updated selinux files on system/vendor part allowing us to have the same selinux policy as the official devices. more about it when its ready
- updated kernel
- released xz2c support

Probably will take a day or two for those to come out.

As for TA - no way, to my knowledge, you can keep it.

PS: Although, if you flash stock back, you should be able to get most of the camera performance back. But there are probably some things that will be missing. Ask at XDA for description
 

The Following 3 Users Say Thank You to rinigus For This Useful Post:
Posts: 233 | Thanked: 532 times | Joined on Sep 2011
#62
thanks, I will wait then a couple of days
 

The Following 2 Users Say Thank You to pagis For This Useful Post:
Posts: 1,414 | Thanked: 7,547 times | Joined on Aug 2016 @ Estonia
#63
I have just released XZ2c images, under releases in https://github.com/sailfishos-sony-tama/main/releases

This work was made possible thanks to lots of testing and feedback by @ApB - thank you! We also fixed dual-sim support, so all dual-sim devices should work properly now.

Meanwhile, I fixed SELinux support that required compilation of AOSP9 bits. For those who have flashed already on XZ2 and XZ3, I recommend to download https://github.com/sailfishos-sony-t...elinux.tar.bz2 and unpack it at / of the device. It contains two files with SELinux policies that will later allow us to switch on SELinux as it is on official devices.

In future releases, flash images will include that fix. If you want to flash now XZ2 or XZ3, I recommend to use images from https://thaodan.de/public/sailfishos...ges/sony/tama/ (dated 3 Dec 2019, check before downloading). Those have SELinux fix as well.

Right now, SELInux is disabled as it mainly makes logs longer. However, this port should be able to follow official devices in this respect.
 

The Following 6 Users Say Thank You to rinigus For This Useful Post:
Posts: 233 | Thanked: 532 times | Joined on Sep 2011
#64
done!flash.sh tho failed to flash vbmeta.img so i had to flash it separetely.
i haven't much time testing it, so far everything works, camera seems to be stuck in high iso somehow, but it's dark now.

more later/tomorrow, great job well done!
 

The Following 2 Users Say Thank You to pagis For This Useful Post:
Posts: 1,414 | Thanked: 7,547 times | Joined on Aug 2016 @ Estonia
#65
Originally Posted by pagis View Post
done!flash.sh tho failed to flash vbmeta.img so i had to flash it separetely.
i haven't much time testing it, so far everything works, camera seems to be stuck in high iso somehow, but it's dark now.

more later/tomorrow, great job well done!
vbmeta bug reported at https://github.com/sailfishos-sony-tama/main/issues/48 , will have to fix it
 

The Following 2 Users Say Thank You to rinigus For This Useful Post:
Posts: 1,414 | Thanked: 7,547 times | Joined on Aug 2016 @ Estonia
#66
3.2.1.20 released, available as OTA and images will be uploaded soon. See release notes at https://github.com/sailfishos-sony-t...3.2.1.20-beta2

Few comments regarding the release:

Camera is not magically cured, that will have to wait for major update in kernel to 4.14. As Sony developers told me, it may require move to AOSP10 as a base. Issue is that in addition to the kernel, few other bits were updated. As a result, we may not be able to just bump the kernel version on our base. However, I will try to update kernel on AOSP9 at some point, probably in 2-3 months - depending on how fast kernel will stabilize on AOSP10. Just let's be aware that it may fail.

If AOSP10 base is needed, expect it to happen somewhere in summer 2020. As in 2019, Jolla gets bits ready for the next AOSP base around that time.

Other changes in release are mainly related to XZ2c and housekeeping.

Thanks to all helping with testing and suggestions!
 

The Following 4 Users Say Thank You to rinigus For This Useful Post:
Posts: 1,414 | Thanked: 7,547 times | Joined on Aug 2016 @ Estonia
#67
@ljo: I wonder whether you have the same issues with the battery life as in https://github.com/sailfishos-sony-tama/main/issues/55 ? On XZ2 and sounds like on XZ2c all is OK, not as bad as on XZ3 in that particular case.
 

The Following 2 Users Say Thank You to rinigus For This Useful Post:
Posts: 102 | Thanked: 187 times | Joined on Jan 2010
#68
@rinigus, I will check. Did not notice before.
 

The Following 2 Users Say Thank You to ljo For This Useful Post:
mankir's Avatar
Posts: 276 | Thanked: 224 times | Joined on Dec 2009 @ Frankfurt, Germany
#69
for better battery life, you can use network mode: 3g. thx to rinigus for the images. i noticed two differences to official images: rsync is not installed and there is this ui showcase: components. wonder if it is possible, to apply a license to tama device...
__________________
MOD-Package: http://talk.maemo.org/showthread.php?t=42415
 

The Following User Says Thank You to mankir For This Useful Post:
Posts: 1,414 | Thanked: 7,547 times | Joined on Aug 2016 @ Estonia
#70
Originally Posted by mankir View Post
for better battery life, you can use network mode: 3g. thx to rinigus for the images. i noticed two differences to official images: rsync is not installed and there is this ui showcase: components. wonder if it is possible, to apply a license to tama device...
That's true in general - cellular data is usually better than WIFI. In that case, we had relatively large consumption without any network. Which I cannot reproduce.

As for rsync/showcase - bit odd, as I have them. Don't think showcase was installed as any pulled dependency.

As for license and corresponding Android emulation - I think its not going to happen. Jolla has been rather clear and stating that they don't want to start supporting unofficial ports. The best way around it for me was to write/support native apps and, if impossible, use some dumb Android phone for extra needed services.
 

The Following 3 Users Say Thank You to rinigus For This Useful Post:
Reply


 
Forum Jump


All times are GMT. The time now is 12:00.