CalyxOS (is coming to) is here for FP4!

Participate Development
, ,
74

Yeah for some reason that was disabled for me already, probably because I played around with Bluetooth settings before, so for me it just worked™ :man_shrugging:

1 Like
75

That’s what they did as default setting in iode newest beta from yesterday as a workaround.

1 Like
76

I read your post when they figured it out, so I probably immediately tried it :smile:

1 Like
77

But it should not be the final solution, because of mor battery drain, because audio streaming is now done in CPU and not in HW. (I don’t notice any difference myself)

And, as I think, it’s not only a calyxOS or iodéOS issue. I think it’s maybe a driver issue in AOSP

78

where? in calyx?
as cde said in matrix, after I mentioned it there, calyx users shouldn’t do it, because it would not work…
But then, I saw in their gerrit, that they do it yourself just like that…strange :wink:

1 Like
79

Or even worse, a Qualcomm issue maybe, since Bluetooth is handled by proprietary blobs. Then we’ll probably have to wait much longer…

You mentioned it in the iode topic, but cde was also at least somewhat right, it didn’t work with the previous version, I think (now I’m not sure I really tried it :see_no_evil:)
Anyways, it’s working now :tada:

The “magic” of Open Source… :smirk:

2 Likes
81

ugh, I did an oopsie and tried to flash Calyx straight from /e/OS, and got stuck in a bootloop. the phone shows the splash screen, vibrates, and reboots again. you think flashing stock FP OS would make me get back on track? my bootloader is unlocked and I never tried relocking it.

82

If you didn’t lock your bootloader you should be fine, I’d just try installing CalyxOS again, they are using some of the partitions pulled from the factory images anyway.

Did you use fastboot flashing unlock_critical before starting the installation? :thinking:
It’s not mentioned in the how-to, but some of the partitions that are being flashed are of the critical variety :smirk:

Oh and just to be clear, there is an automatic reboot before the installation finishes, the boot, vendor, product and so on… partitions are flashed through the update mechanism in fastbootd / recovery (or at least it looks like that :man_shrugging:) are flashed separately (preceded by a reboot to fastboot again), maybe that’s what you have been seeing or where your issues start?

2 Likes
83

at first I didn’t notice that, and rebooted too quickly, but then I tried flashing again and that time I waited until the command finished doing it’s stuff. I’m still stuck in a bootloop.

fastboot flashing unlock_critical is apparently one of the commands in the Calyx’ flash-all.sh script already (disregard, that’s the command I tried manually after reading your post, apparently I’m very easily confused):

fastboot flashing unlock_critical
FAILED (remote: '       Device already : unlocked!')
fastboot: error: Command failed

also, in the output I’m seeing several commands throwing “archive does not contain X” messages, like archive does not contain 'vbmeta_vendor.img'. I’m not sure if it’s a message because of some repurposed script, or am I missing some files, despite having verified the .zip file I downloaded from CalyxOS website.

edit: okay, I had to manually factory reset the phone (I thought the installer would take care of that?!) and it booted!

1 Like
84

Well there is fastboot update -w in the script, so it should wipe userdata :thinking:

I’m glad it works now :+1: still a strange issue though :man_shrugging:

Just for the record, what’s the state of fastboot flashing get_unlock_ability?

1 Like
85

$ fastboot flashing get_unlock_ability
(bootloader) get_unlock_ability: 0
OKAY [ 0.001s]
Finished. Total time: 0.001s

1 Like
86

@hirnsushi
If you’re still testing, could you please do a test?
Unfortunately I don’t have a test device.

Because of the unlock_ability=0 problem after a first reboot after installation.
Please test if the problem also exists if you don’t reboot via the extended boot menu, but always just run the “adb reboot” instead.

If it makes a difference, it would also be interesting to see if it is the same in iodéOS and FPOS.

Thanks very much

87

That shouldn’t make a difference, I always run adb reboot / fastboot reboot instead of using the menu when flashing devices :man_shrugging:

But since I wanted to test what happens if you don’t reboot anyways, might as well test if there is different behaviour somewhere :+1:
I’ll follow this up in the other topic, since I’m only testing FPOS on the other device for now.

Edit: Just to clarify this part:

get_unlock_ability gets reset on the first regular boot, so once you reached full userspace it’s already too late. Or did you mean something else with extended boot menu? :thinking:

1 Like
88

My thoughts were as fallows:
Is there maybe a difference to reboot, after first restart, in bootloader to unlock to bootloader if you restart via extended boot menu “long press power buttton/restart/bootloader” or via “adb reboot bootloader”?
Is in both situation the unlock_ability reset to 0?

But, maybe it makes no diffence. It shuold not…

89

I’m still not entirely sure what you mean by extended boot menu, sorry.

If we are talking about the menu that pops up when long pressing the power in a regularly running system, you already went to far to prevent it. The same goes for adb reboot, at that point the flag has already been changed.

If you mean the bootloader menu, I have tried every possible way to reboot the phone before the first start, as documented in the other thread. As long as you don’t boot into proper Android it’ll stay on 1, as soon as you start the regular system it’ll change, haven’t found a way around it (yet) :man_shrugging:

1 Like
90

there’s a new update, 3.5.1:

Location indicator and Safetynet fix

those of your who run Calyx, have you managed to make the phone find the update? I’ve been checking for the past few days with no results. Calyx doesn’t support root and/or unlocked bootloader, so they won’t assist with that.

91

So do you have an unlocked bootloader? I think (but I am not 100% sure) that CalyxOS will only receive the updates if the bootloader is locked.

Anyway, I have it installed. Very soon after I switched on my phone (bootloader locked), the updater was downloading the update and all I had to do was to restart.

92

So if understand you correctly you rooted your phone?
Then the regular procedure applies:

That’s how I update my Calyx installation as well, otherwise the installer will just stop.

2 Likes
93

So if I understand you correctly, a locked bootloader is not mandatory to receive OTA for CalyxOS?

94

Nope, it works just fine unlocked :smiley:
The installer only fails because it’s checking the hashes for the partitions it should be updating and since Magisk changes the boot partition it will stop and throw an error.

2 Likes