Camera is not capable of recording images "external storage not writeable"
-
@mlinodasilva
Did you try to reinstall with ubports installer (without wiping anything) ?EDIT: this problem seems to be recurrent and not just limited to the meizu phone, see these threads:
If i said my device works great, it's because it's same brand,
same SOC brand, and to let you know this issue is not general to this brand nor to all uTouch devices. -
Well its a fact the camera can work fine ith a Meizu Pro 5, since I used it for years with the last OTA without any issue. The problem seems to lie with the fact that upgrade to the current OTA seems to break the camera in several devices and apparently no workaround/reason for this code regression has been found.
The reason I'm reporting this issue so late is that I just recently upgraded to the last OTA, way later than most. Actually I've kept an image of the last OTA and I might just revert to it since I lost the scopes and the camera without any relevant improvement from upgrading to the current version, quite the contrary.
PS: Yes, I did upgrade to the current OTA using the recommended installer from the website.
-
@mlinodasilva
Hi, I moved your thread to the appropriate device category.
BTW I suspect you're on stable OTA15. OTA 16 is on its way with major changes so you might want to try the RC channel and report the issue if it is already there. -
Well nobody reads the device-specific subforums, I posted this same issue there along two other ones and there was no reply. Plus as posted before, this is not a Meizu-specific issue since other phones have reported this.
I am on development OTA-15. I started in stable
I have tried upgrading to no avail as I already mentioned in the first post:- Release Candidate: same issue
- edge: same issue
- Development: same issue.
The only version where the camera works is OTA-14, and I might just revert to this version instead, since losing the camera is a big no in my book.
I'm happy to report the issue in the appropriate venues (github, etc...) since this is, I repeat not a Meizu5 -specific issue.
Cheers
-
@mlinodasilva
Device specific subforums don't have the same public and Meizu owners on the forum are pretty rare.About your issue, this is not a bug in Ubuntu Touch but it touches few devices, maybe because they share the same chipset or drivers...
And sure, you can report it to github, but also the thread you mentioned earlier is 2 years old and before OTA14 IIRC it is probably not the same issue. I don't know where you got the idea that OTA broke the camera on multiple devices.
Camera not working is a big no for many users so it drag attention as we all understand. -
@applee said in Camera is not capable of recording images "external storage not writeable":
but also the thread you mentioned earlier is 2 years old and before OTA14 IIRC it is probably not the same issue
I tried to tell him already... No result
-
Allright, this is not helpful at all guys, sure that might not be a common issue but it is an issue reported by several people around here.
Fow all its worth, I'm sorry for not being clear I did not upgrade from OTA-15 but from ubuntu-15 (vivid) the version originally from canonical that still had the scopes, apologies for this I'm a bit dislexic and I mix-up things a bit sometimes.
Back in the days this used to be a very useful resource to troubleshoot issues and get the software to work on several devices, I guess things have changed. I was expecting some advice along the lines of checking in terminal about troubleshooting the /dev/whatever the camera is since the camera takes pictures but cannot make the final step of recording them from RAM to the internal storage or sdcard. Instead all I got was "don't bother, this is an old issue, you have an old model and no-one cares".
I'm just going to re-flash the image of vivid ubuntu I made before upgrading, sure I'll go back to an outdated browser but at least I'll be able to take pictures again.
Thank you for all the useful advice, you've been a great help.
-
@mlinodasilva
People are willing to help but when you talk about "last update gave me this issue" and refers to a 2 years old thread...
How could we say "yes, it's the same issue, that came with last ubports update"?They are lot of issues, some make you believe multiple devices get the same, but that's not that simple.
If you want to help dev so they can help you, give logs of the crashing.
The fact is, you, and i, own [old] phones that tend to disapear, and so, it's hard to get feedback for the devs.
One question though, did you try to install from scratch?
If not, maybe you should backup what you need to backup (contacts, sms, music... all your personnal data...), and then flash uTouch canonical image (not yours, a "virgin" one) with SP Flash Tool (if it's a mediatek SOC), and then use ubports to flash last ubports OTA15?
I did this to migrate from Canonical OTA-15 to ubports OTA-12.
This way, you're sure nothing will remain from previous install and from canonical era.EDIT : as i see it's not a mediatek device, so unless there is another method to reinstall from scratch on this device, just backup all your personnal data, and then reinstall wiping all you can wipe with ubports installer.
-
@mlinodasilva
Ok things are more clear now.So I don't know if the camera works with UBports on the Meizu Pro5.
If this bug linked to the Pro5, then I'm sure it has been reported (as I understand you know).
In this case the issue is probably hard to fix.If the bug has not been reported, you should do it (if not already).
And to help out people that come here to help, could you give us the link to the issue you discovered/submitted ?
This would be helpful.Thinking about switching from canonical version of UT maybe some files in your home directory might have different rights.
And as @Keneda said, you might wanna try a full installation.
Save your personal data of course and then using the installer with the wipe option will give you a fresh start with UT.Best of luck
-
Hi @mlinodasilva,
If you're willing to check Ubuntu Touch OTA-15 out again, I want to know why you're receiving this permissions error. Maybe you can send me a private message on the forum when you're available and we can try to debug a little faster? Then we can post any results back to this thread.
