Hi Everone!
RCS is aiming at replacing SMS in a near futur.
Any plan to support it ?
Cheers
wilfridd

Hi everyone,
Thanks and honours to the UBports team for the great achievement so far! Thanks to make the whole thing moving forward.
I made my journey testing the 16.04/devel on my MX4 and wrote down my experience in a Calc spreadsheet. I'd to ask whether it's useful to share the file or not... It might be some kind of interest to gather experience to help developers ? No question to challenge Github of course...
Cheers,
W.

Hi Matthias,
You should get a system phone call code from your operator. It looks like ( remplace + with stars **)
++systcode+other.numbers.followed.by.your.phone.number++seconds.to.ring.before.voicebox#
Use the phone app to send the whole thing, press the green call button and voila...
The code might be different for you obviously, but anyway, it's triggered by the operator. Give a call to helpline...

BR

W.

@oli.sax , Flohack & WLBI

At the EoD , Anbox wouldn't be a sustainable solution to run WA. Some month ago, I managed to make WA successfully work on Anbox/Xenial...but after a couple of weeks, it stopped suddenly... I upgraded the WA apk, reinstalled...nothing... After lots of retries I got an error message saying approx. "You have a custom Andoid rom installed, WA doesn't support...blabla..." .... End of the story.

I totally agreed with all opinions and all that has been said on WA...
Nowadays I some times use LoquiIM, which finally (voodoo magic?) stop displaying the sadly famous "decrypt error“ message after about 2.5 month...

W.

@Stefano
Many many thanks! I think that might work. I'll try and keep you posted

@Stefano
Thanks for the url ! but same here :

• Send the photo of the sticker on the box or back cover

I have the IMEI and SN, I could try the "photo editing" ... Would you agree to share a picture of your box, provided that you mask our IMEI and SN ? (feel free to send here)
I think my last chance to get UT on this device...since I can't find the previous owner.

@Stefano
each tries to log in flyme.cn have same result, it complains "You have not logged out as <some account name at flyme.cn>. To log with another flyme account, please log out properly first."
It seems the previous owner has registered the device with his account in flyme.
Kind of similar to AppleID.
That why I contacted meizu support, But to deregister, they said they need a picture of the original box with IMEI and SN sticker on it.... lol... which I don't have because the device is second hand.

@Stefano
Hi Stefano,
Thanks for your reply.
Volume down + power on shows :
=> Fastboot mode (locked, unrooted)
hardware is TD-LTE, 64GB with cn rom 5.1.3 (I can up/downgrade but only with chinese FW). With other (intl FW), I get a "Firmware corrupt" same as decribed in other posts.

I've found windows tools here http://xep.8800.org/pro5/ and currently trying to flash but to no avail since command "fastboot devices" show nothing (on linux it gives the serial#)

Thanks again for help.

@Marathon2422
hi,
thanks for reply.
it's a 64gb, cn rom with l tde hardware... sounds bad.
Not sure I can move forward with root not enabled, can I?

Hi @AppLee
Thank for fast reply.
I already got IMEI and SN (from Android settings) and provided to the meizu support... but they requests a picture of the original box ... I thing IMEI and SN should be sticked on the box... and and don't have it.
I'm stuck here...
Does any PRO5 owner on this forum have such original box ?

Hi,
I finally got a pre-owned Meizu PRO5 in a second hand shop. Chinese FW 5.1.3, fastboot locked, unrooted. Before proceeding with UT install (very good post available on the forum, btw), I first need to enable root, and registering the phone with a flyme account is required.
As the phone is still linked to the previous owner Flyme account, I contacted Meizu Support to request for a log out. But the problem is Meizu Support asked for the IMEI and SN that states on the surface of the original phone box ... Dang...! I don't have the original box.
Anyone could help, please ?
Thanks
nauvpp.

Hi,
Does anyone succeed to have GPS working on MX4 ?
Based on my experience and tests:
uNav, Pure Maps (btw, tremendous nice SW), Gmaps never ever got FTTF, even lying the phone outdoor for hours.

uSensor finds supported backend and active, no error in source status , but still no position infomation (lat, long, etc)

sudo gps_test shows sometimes gps info, but ends systematically with a segfault:
#############
*** setup signal handler
*** get gps interface
*** device info
id = gps
name = Hardware GPS Module
author = The MTK GPS Source Project
*** init gps interface
** Creating thread: 'GPS NATIVE THREAD' (start=0xb6cd2d79, arg=0xb6cdba54)
** After thread_create: 'GPS NATIVE THREAD', error=0 (start=0xb6cd2d79, arg=0xb6cdba54)
**** Thread wrapper start (start=0xb6cd2d79, arg=0xb6cdba54) ****
*** set capabilities
capability is 00000001
*** setting positioning mode
*** start gps track
*** status callback
*** engine on
*** status callback
*** session begin
*** gps tracking started
*** tracking....
*** nmea info
timestamp: 28983000
nmea (69): $GPGGA,235944.000,8960.0000,N,00000.0000,E,0,0,,137.0,M,13.0,M,,*4E

*** nmea info
timestamp: 28983000
nmea (45): $GPGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*30

*** nmea info
timestamp: 28983000
nmea (71): $GPRMC,235944.000,V,8960.0000,N,00000.0000,E,0.000,0.00,050180,,,N*40

*** nmea info
timestamp: 28983000
nmea (39): $GPVTG,0.00,T,,M,0.000,N,0.000,K,N*32

*** nmea info
timestamp: 28983000
nmea (23): $GPACCURACY,3162.1*3F

Segmentation fault
##############

Any chance to debug or fix?
BR,

@Lakotaubp thanks!

Hi Everone!
RCS is aiming at replacing SMS in a near futur.
Any plan to support it ?
Cheers
wilfridd