Unfortunately, ______ has stopped
Added by Mike Turneep almost 7 years ago
Hello folks
I am new as a Replicant user, but I'm trying to move to Replicant 6.0 on an i9300 as my sole phone now.
The OS install went smoothly, and I find it very refreshing to be on a clean system which serves the interests of me as the owner of the phone.
But I'm having issues with apps. The worst hangup by far, and one that will drive me off to some other ROM if I can't find a solution, is that trying to place voice calls in OWS Signal fails and crashes the app, giving the message "Unfortunately, Signal has stopped".
The Wallpaper Picker also crashes with a corresponding message if I try to pick an image through that. I think there have been some others as well but if so, I can't recall which right now.
Does anyone here have an idea why these things occur? Method to find out? Solution?
I speculate that it may have to do with SELinux profiles, which I've never worked with and I haven't modified the ones in Replicant 6 from stock. But it is nothing more than speculation.
A couple of other things:
How does it work with updates to the system? Do I need to manually reflash once in a while? Or are security updates pushed from the Replicant project? Or could I subscribe to updates from LineageOS?
And I noticed that I generally can't update the F-Droid privileged extension (or F-Droid itself?). Not that I care much for the new F-Droid design anyway, I much prefer the searchable lists to the swipey Market lookalike, but isn't the version locking likely to become a problem sooner or later?
Replies (3)
RE: Unfortunately, ______ has stopped - Added by Gu W almost 7 years ago
Hi,
The worst hangup by far, and one that will drive me off to some other ROM if I can't find a solution, is that trying to place voice calls in OWS Signal fails and crashes the app, giving the message "Unfortunately, Signal has stopped".
I am having the same issue with Signal. My guess is that voice calls on Signal are crashing, because Signal requires the ability to play videos, even though you might only want to make a voice call. Right now playing videos is not supported on the i9300. I guess the phone needs to support both video and voice, because both call variants are interconnected in Signal. I assume this, because on Riot, there are two different options: voice call and video call. However, Riot only crashes when choosing "video call" (the crash is similar to Signal's). Your best chance is probably to file a new issue on Signal's GitHub page: https://github.com/WhisperSystems/Signal-Android/issues or to comment on this already existing issue: https://github.com/WhisperSystems/Signal-Android/issues/6583 ...and hope that moxie is interested in supporting Replicant or any other OS with non-working video playing ability. Alteratively you could try making displaying videos work on Replicant (probably more work).
How does it work with updates to the system? Do I need to manually reflash once in a while? Or are security updates pushed from the Replicant project? Or could I subscribe to updates from LineageOS?
I guess right now you will have to reflash after every new release (factory reset should not be needed).
And I noticed that I generally can't update the F-Droid privileged extension (or F-Droid itself?).
F-Droid and the extension work on my device. Right now there is an annoying message to update the privileged extension but except for that it should be working.
RE: Unfortunately, ______ has stopped - Added by Mike Turneep almost 7 years ago
Hi Gumbor,
Thanks! That's an extremely helpful answer.
Since this is a bad time to be unavailable on my only working phone I opted for switching to LineageOS for now.
And now it's all working fine in terms of encrypted calling and not crashing, except of course that I'm now running a lot of the icky parts Replicant gets rid of...
I did capture some logs before going and will make sure to add to the discussion over at WhisperSystems' issues though.
As much as I would like to be of help getting video on Replicant to work, my Java is rudimentary and I have virtually no experience with systems programming, especially on phones, so the threshold's pretty high to being useful there. I'd probably be of better use some other way.
Thanks also for the clarification on updates. I guess if the factory reset isn't necessary it should mostly leave the software and configuration working. Not that bad doing it manually then, though it would be great to have automatic updates or at least reminders.
F-Droid and the extension work on my device. Right now there is an annoying message to update the privileged extension but except for that it should be working.
They were working just fine on my device as well, but since they come signed with a different key than that in the repositories upgrading requires uninstalling them first. At least I think it was an issue for both F-Droid and the Privileged extension. I'm only really sure about the extension, and now I can't check...
No real issue for now, but what I ask myself is what happens if a severe vulnerability is discovered and it really needs to be upgraded?
RE: Unfortunately, ______ has stopped - Added by Kurtis Hanna almost 7 years ago
I created an issue for the Signal call failures: https://redmine.replicant.us/issues/1810
Please add anything else you can think of to the ticket.
If you are interested in testing potential fixes, please let us know in the ticket as well.