SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview - Page 117 - maemo.org

ryanml | # 1161 | 2020-11-02, 16:42 | Report

Great work! Though I think I personally will hang back on 3.3.0.16 until there's a known workaround for AD though

edp17 | # 1162 | 2020-11-03, 01:20 | Report

Originally Posted by edp17 View Post

Here is the fixed 3.4.0.24 build (CM12.1). Vibra and sensors are fixed. AD still doesn't start.

I have managed to fix AD!

Note: The root cause: the default user nemo has changed to defaultuser.
Therefore this change is only needed on new installs.
If you OTA to release 3.4.0.24 (not available yet) you probably won't need to do this, as the nemo will be kept as default user.

So, to make it work, you need to edit two files:

/opt/alien/system/script/alien_start_guard.sh
change:
Code:
```
SYSTEM_USER_NAME=nemo
```
to:
Code:
```
SYSTEM_USER_NAME=defaultuser
```
/opt/alien/system/script/platform_envsetup.sh
everywhere in this file change: nemo
to: defaultuser

After these changes AD should start as normal.

Last edited by edp17; 2020-11-03 at 01:39.

The Following 2 Users Say Thank You to edp17 For This Useful Post:
ryanml, sailor

ryanml | # 1163 | 2020-11-03, 01:53 | Report

Awesome! I'll give this a shot tomorrow, thanks for your amazing work as always

ryanml | # 1164 | 2020-11-04, 04:13 | Report

Worked great, excellent work! 👍

edp17 | # 1165 | 2020-11-04, 11:29 | Report

Originally Posted by ryanml View Post

Worked great, excellent work! 👍

I am glad it works. Enjoy.

edp17 | # 1166 | 2020-11-06, 23:10 | Report

If somebody interested I have created a boot logo.
To install you need to flash the edp17-hammerhead_sfos-bootimage.zip in recovery.

When my phone boots it looks like:

When it is on the charger:

If you would like to go back to (slightly) original, just flash this: hammerhead_no-padlock-bootimage.zip. (In this one, there is no padlock image at the bottom.

)

Enjoy.

The Following User Says Thank You to edp17 For This Useful Post:
sailor

LinuxLounge | # 1167 | 2020-11-20, 09:06 | Report

Originally Posted by edp17 View Post

I have managed to fix AD!

Note: The root cause: the default user nemo has changed to defaultuser.
Therefore this change is only needed on new installs.
If you OTA to release 3.4.0.24 (not available yet) you probably won't need to do this, as the nemo will be kept as default user.

So, to make it work, you need to edit two files:

/opt/alien/system/script/alien_start_guard.sh
change:
Code:
```
SYSTEM_USER_NAME=nemo
```
to:
Code:
```
SYSTEM_USER_NAME=defaultuser
```
/opt/alien/system/script/platform_envsetup.sh
everywhere in this file change: nemo
to: defaultuser

After these changes AD should start as normal.

Excuse my ignorance but what is AD? Is it Alien Dalvik or something else?

LinuxLounge | # 1168 | 2020-11-24, 00:43 | Report

Followed the instructions exactly but can't get past the bootlogo, the modified CM12.1 won't boot either, any ideas?

edp17 | # 1169 | 2020-11-24, 14:14 | Report

Originally Posted by LinuxLounge View Post

Followed the instructions exactly but can't get past the bootlogo, the modified CM12.1 won't boot either, any ideas?

A few questions:[LIST][*]What instructions exactly have you followed? Instaling SFOS on the Nexus 5, upgrading an SFOS version to another or changing the boot logo?[*]How do you mean "modified CM12.1"?[*]Multirom or single rom environment are you using?[*]Are you using kexec kernel? (Recommend to read this topic.)[*]What Android version was it on the device before you started?[*]Sili question, is that device a Nexus 5 or a 5X?
[/LIS]

LinuxLounge | # 1170 | 2020-11-24, 19:04 | Report

Originally Posted by edp17 View Post

A few questions:[LIST][*]What instructions exactly have you followed? Instaling SFOS on the Nexus 5, upgrading an SFOS version to another or changing the boot logo?[*]How do you mean "modified CM12.1"?[*]Multirom or single rom environment are you using?[*]Are you using kexec kernel? (Recommend to read this topic.)[*]What Android version was it on the device before you started?[*]Sili question, is that device a Nexus 5 or a 5X?
[/LIS]

Hi, I'm having the same issue in a single rom environment, without kexec kernel, it was on stock before I started and it's definitely a Nexus 5