![]() |
Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release
Quote:
If that doesn't work, I would check the integrity of the sailfishos image you downloaded with sha256sum as example. I compared two files I have here and can give you the checksum: sha256sum sailfishos-hammerhead-release-2.1.0.10-build0.3.zip Code:
e4ed3f248918284c3bb8e2a76e3b07aa31ab131d6c34a25805efebdc706ca1f5 |
Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release
Thanks its working now. One more question: How is it possible to update to a new rootfs image released by you without loosing previous data?
|
Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release
Quote:
In the meantime you have to backup/restore your data and do a fresh installation of the newer image. I refer to this post, I made some time ago, where I described my way to do backup/restore. http://talk.maemo.org/showpost.php?p...&postcount=238 For Contacts/Calendar Code:
devel-su pkcon install nemo-qml-plugin-contacts-qt5-tools Code:
pkcon install nemo-qml-plugin-calendar-qt5-tools |
Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release
I really would like to update my 2.0.4.13 because some new apps require the new QT version, but I also need the Android compatibility...are there any news about Sfdroid or Anbox?
|
Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release
Quote:
The other developers liar/krnlyng and saidinesh have been busy recently and have had very limited to no time to able to help. |
Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release
What is the state of this build? I have a spare Nexus 5 to flash. Should I use this one, or one based on cm 12.1?
|
Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release
Quote:
|
Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release
Quote:
|
Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release
The topic should be changed: SailfishOS 2.0 -> SailfishOS 2.1
|
Re: SailfishOS 2.0 Nexus5 based on CM13 alpha release
I'm currently running a custom kernel with the file name:
Code:
sfos_custom_kernel_v9-btsleep-100hz.zip I could swear there was a link pointing to the download of the custom kernel mentioned in post #2. Anyways. I initially had problems with enabling WIFI due to a naming mismatch between the kernel's uname and the original kernel's uname, resulting in differently named /lib/modules/[uname] directories. (module could not be found) In case of anybody else running into the same problem: could resolve the issue by simply renaming (or cp -afr) the directory to the proper name, reported by `uname -r`. Code:
# ls -1 /lib/modules |
All times are GMT. The time now is 08:46. |
vBulletin® Version 3.8.8