Posts made by mlinodasilva

@keneda

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.

@applee

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

@keneda

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.

@keneda

1. I'm happy your camera app works with your MX4, but, personally speaking, I'm a tad more worried that it stopped working with my Meizu Pro 5.

2. I postponed upgrading to the current OTA since I enjoyed Scopes a lot and I postponed the update as much as I could to avod losing them. Little did I know that I would end up not only losing them but also losing my camera functionality so you'll forgive me if I'm a bit miffed at it.

I guess I'm getting the same issue more than one year later indeed, seems unfortunately like it wasn't solved in between.

Cheers,

Mario

Apparently this subforum is a place where posts die alone, but anyway, I found a solution that solved this problem, hopefully it will be useful to others that may have the same issue:

I deleted the cache in the terminal (command "rm -rf .cache") and everything went back to normal.

I'm on a Meizu Pro 5, and after an OTA upgrade the camera stopped being able to record images and videos, either to the internal storage or the SD card.

I get the message:

"External storage not writeable
It does not seem possible to write to your external storage media. Trying to eject and insert it again might solve the issue, or you might need to format it."

The camera app has access to the camera and microphone, so this seems a bug. Does anyone know how to fix this?

Tried:

• rebooting
• ejecting and reinserting the sdcard
• deleting the .cache folder
• switching to edge and updating the phone and reinstalling all apps

nothing works.

EDIT: this problem seems to be recurrent and not just limited to the meizu phone, see these threads:

https://forums.ubports.com/topic/2596/camera-app-doesn-t-work

Another issue I have with my Meizu Pro 5 is that I have to re-insert the configurations and passwords for a WiFi SSID each time I turn off/reboot the phone.

Then the new SSID is recorde as SSID 1, SSID 2, etc...

I know this is an issue not specific to Meizu phones, but I was wondering if a workaround has been found to this problem? A look at the other thread discussing this issue didn't yield any useful workaround...

for reference:

https://forums.ubports.com/topic/2406/wifi-password-loss-after-each-and-every-reboot-on-meizu-pro-5/93

As the title says, for some reason my music tracks appear duplicated on the music app, athough only one such mp3 file appears. The issue appeared randomly in the last OTA, and moving recently to OTA15 (which was the reason I upgraded) did not fix the issue either.

I was wondering if someone else has had this specific issue and if a workaround can be found. It is pretty annoying since I'm forced to each each song twice.

Thanks for the help!

As the title says, I finally decided to update to the new OTA, and I cannot store pictures with my camera, it says "capture failed replacing your external media, formatting it or restarting the device might fix this problem" same if I switch to internal media.

This seems to be a bug, since the filesystems are definitely writable and the directories accessible (checked in terminal with ls -la).

Wondering if someone else had this issue and a solution exists.

Thanks in advance!

To put the phone in loud speaker mode, once the call starts, you can tap the icon with the speaker and an x and the call will be put in loud speaker mode, which means that you and the people next to you can hear the person who is calling, and further, the people calling can hear people speaking nearby. Some call it conference mode too.

My question regarding this issue is: OK if this is an hardware bug, does this mean that the phone has two sets of speakers? one for the regular call, and another for the loud speaker/conference mode?

Because if there only is one speaker in the hardware, it cannot be anything else than a software bug since the speaker works pretty well (playing musing and such).

I'm willing to believe I'm having an hardware issue, but I'd like to be sure before disassembling the phone again (I had to repair a broken glass once).

I have a reated but slightly different issue:

On my Meizu 5, I cannot hear the call unless I am using headphones or putting in loud speaker mode. Pretty annoying, and it must be a software bug since using the phone in loudspeaker mode does work.

I eve tried uVolMan to no avail. I resorted to using the phone with headphones exclusively...

One thing that bothers me in ubuntu touch is the fact that headphone buttons (like play/stop/answer/finish call, volume up, volume down) never worked, is this a feature that could be considered in the future?

It is pretty much convenient and quite standard in other cellphones OS.

Another thing: Since we moved to ubports, there is a nice feature that was the music app automatically downloading album covers/artist pictures for our media library. Any chance we could have it back?

I have some more questions regarding Meizu on ubports:

1. If I place a phone call I cannot hear anything unless I plug the phones or put it on loudspeaker? Is this a bug or do I have to put some feature on somewhere in the options?

2. The calls and ams scopes no longer exist? They were very useful... How can I get a listing of the phone calls history with ubports?

Sorry for not being clear, by 'chip' I meant the SIM

Anyway I can share my experience with ordering my spare screen: As you can imagine, it was not easy. First of all Meizuworld was a no go, they don't seem to accept orders from outside China. So I registered an account in aliexpress and made a search for a replacement screen. I was a bit weary from ordering from some random supplier there so I decided that I would pay through paypal to have some sort of protection. This already limited my options since most of these China suppliers don't accept paypal. Still I was left with about 10 stores with an acceptable range of prices. Then I put orders for the screen with int. Shipping and in 3 cases I got refunded and my order cancelled with no explanation. At the 4th attempt a supplier from Hong-Kong did ship it. 1week attempts at purchasing plus about 3weeks shipping (with very nice tracking and packaging). I also ordered a plastic case for my phone from another supplier using the same method. doing

This is what I would suggest doing, but it takes time...

Heh, it seems I have a string of bad luck regarding this phone (in between the hassle it was getting it from China, then flashing canonical ubuntu, then breaking the screen, trying to get a replacement one, the ubports).

I tried anther chip and it works, so for some reason my SIM is malfunctioning, will get a replacement one...

I've been slowly reinstalling stuff, I noticed that the GPS has trouble working, although it seems to be recognised, but I remember it was already difficult when indoors during the days of canonical. Accelerometer works, but the compass app doesn't seem to be working. Minor hurdles...

Anyway, by request I uploaded my ubuntuimage folder from /root/.cache the link is below:
https://www.dropbox.com/s/0464g6vpm6kzgsb/ubuntuimages.tar.gz?dl=0

@Stefano this is to try to solve the issue
With the phone not detecting the SIM card? Did anyoneelse have this issue in the past?

Update: Don't try to rsync your old canonical home folder in ubports, everything gets stuck, I'm in the middle of wiping my data folder and reflashing again

It's gonna be a pain in the ass re-importing the contacts, calendar, etc... is there a list of the relevant hidden folders anywhere?

@hans1977se I can upload my /root/.cache/ubuntuimages I haven't deleted it yet, would that be of interest?

@Stefano That worked thank God!! I had an additional difficulty the recovery couldn't flash the data partition for some reason so I reformated it, I suspect the issue might have been lying there. For the sake of it I tried ubuntu-device-flash and it still didn't work, but this time he got stuck on a progress bar.

Anyway I flashed all the partition images you sent me, and soon enough I had ubports booting!

I cannot state how much I am grateful for your help, you have been most kind in helping me, I was going nuts oer this. THANKS!

Now I just have to figure out how to make my SIM work again (I never could get it to work in anything else than the slim slot with the canonical image, and now it doesn't seem to recognize the sim in any of the two slots, but thats probably an hardware fault I have had since the beginning, these meizu 5 phones are known to have random hardware issues).

In any case, I have internet, camera, and hopefully GPS already working, so it's already a nice start. Thanks again Stefano!

@hans1977se alright, decompressing the version1.tar.xz yields these files:

720.0 # tree
.
|-- system
|   `-- etc
|       |-- system-image
|       |   |-- channel.ini
|       |   `-- config.d
|       |       |-- 00_default.ini -> ../client.ini
|       |       `-- 01_channel.ini -> ../channel.ini
|       `-- ubuntu-build
`-- version-1.tar.xz

as for the keyring file:

729.0 # tree
.
|-- device-60f53a5768e9340729d3a5ef9263bd3a9726792e7d0dbf830e5b124938dd419a.tar.xz
|-- device-60f53a5768e9340729d3a5ef9263bd3a9726792e7d0dbf830e5b124938dd419a.tar.xz.asc
|-- keyring-4c4e7ef380ebcfa2c31084efa199138e93bfed8fc58aa3eb06bdf75a78af9b57.tar.xz
|-- keyring-4c4e7ef380ebcfa2c31084efa199138e93bfed8fc58aa3eb06bdf75a78af9b57.tar.xz.asc
|-- system
|   `-- usr
|       `-- share
|           `-- system-image
|               |-- archive-master.tar.xz
|               `-- archive-master.tar.xz.asc
|-- ubports-d50c18b27590af5734a826c4f7857d8909b0e0f902d21af142a780620c8eb58b.tar.xz
`-- ubports-d50c18b27590af5734a826c4f7857d8909b0e0f902d21af142a780620c8eb58b.tar.xz.asc

In any case couldn't it be possible to manually download the kernel files and flash them like I did originally for the canonical ubuntu-touch? I used the method from this link: https://askubuntu.com/questions/767323/how-to-install-ubuntu-on-meizu-pro-5-that-was-originally-with-android

I would need a kernel-OTA-15.zip (with boot.img, dtb, logo.bin, ldfw), ubuntu*.tar.xz, device*.tar.xz, custom*.tar.xz, version*.tar.xz. Basically doing whatever worked in the past with canonical...

Anyway, there seems to be nothing wrong with my partition table as shown by the command below...

746.0 # adb shell sgdisk --print /dev/block/sda | grep -v GUID
Disk /dev/block/sda: 7633920 sectors, 29.1 GiB
Logical sector size: 4096 bytes
Partition table holds up to 128 entries
First usable sector is 6, last usable sector is 7633914
Partitions will be aligned on 64-sector boundaries
Total free space is 11386 sectors (44.5 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            1024            1279   1024.0 KiB  0700  private
   2            1280            1343   256.0 KiB   0700  proinfo
   3            1344            1407   256.0 KiB   0700  misc
  21            2048            3071   4.0 MiB     0700  param
  22            3072            5119   8.0 MiB     0700  efs
  23            5120            5631   2.0 MiB     0700  pnv
  24            5632            6655   4.0 MiB     0700  ldfw
  25            6656            7679   4.0 MiB     0700  dtb
  26            7680           13823   24.0 MiB    0700  bootimg
  27           13824           22015   32.0 MiB    0700  recovery
  28           22016           30207   32.0 MiB    0700  bootlogo
  29           30208           35327   20.0 MiB    0700  rstinfo
  30           35328           40447   20.0 MiB    0700  mnv
  31           40448           45567   20.0 MiB    0700  reserved1
  32           45568           50687   20.0 MiB    0700  reserved2
  33           50688           55807   20.0 MiB    0700  reserved3
  41           65536          720895   2.5 GiB     0700  system
  42          720896          851967   512.0 MiB   0700  custom
  43          851968          983039   512.0 MiB   0700  cache
  44          983040         7633914   25.4 GiB    0700  userdata