[Ubuntu-phone] click + ubuntu-touch + cocos2d-x

[Ionut Negru]

Hi,

I have built a yellow-world app with cocos2d for ubuntu-touch and I wonder
where I could find a documentation to learn how to link/install
automatically on the device the third party packages it is dependent on. Is
there a guideline on how to deploy on ubuntu-touch an app that depends on
various packages not installed by default with the system image?

Thanks,
Ionut
-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] click + ubuntu-touch + cocos2d-x

[Ionut Negru]

Hi Benjamin,

I have solved the dependencies issue and thank you for that. However the
app fails to initialize OpenGL and I think I need to link cocos against
libgles ... but there is a chain of issues starting from this and I am
currently working on it. If I succeed to run cocos on ubuntu-touch I will
write the guideline.

Regards,
Ionut

On Tue, Sep 15, 2015 at 7:59 PM Benjamin Zeller <
benjamin.zel...@canonical.com> wrote:

> Hello Ionut,
> >
> > Hi Benjamin,
> >
> > Thank you for the information ! I will include the missing
> > dependencies in the click package and hope for good results.
> >
> please let me know if it did work out for you. Creating an example
> project / tutorial out of what you are doing
> is interesting for everyone. It's always good to have some examples :).
>
> Regards,
>
> Benjamin
>
-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] The problem with "no background processing for apps"

[Ionut Negru]

Please excuse my ignorance, but what is this IOS? Is the OS shortening from 
operating system?


On Friday, October 9, 2015 1:02:21 AM EEST, Selene Scriven wrote:

* Oliver Grawert  wrote:
(note that this is pretty close to the IOS model (which shows 
this is techincally possible) and is the reason that we are 
currently miles better in battery life than android in the same 
device)


It sounds a lot like the PalmOS model from the 90s.  It didn't 
really have multitasking; it was more DOS-like.  Apps were 
expected to save complete state and exit when losing focus, then 
resume where they left off when started again.


The PalmOS approach actually worked pretty well.  The best PDA I 
ever used was a Palm m500, their last monochrome-screen model.  
It wasn't a phone and it didn't have any networking built in, but 
it was good at what it did.



-- Selene





--
Sent using Dekko from my Ubuntu phone

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] The problem with "no background processing for apps"

[Ionut Negru]

:)

On Friday, October 9, 2015 7:33:19 AM EEST, Nathan Haines wrote:

On 10/08/2015 09:24 PM, Ionut Negru wrote:

Please excuse my ignorance, but what is this IOS? Is the OS shortening
from operating system?


iOS is the system software that runs on Apple's iPad and iPhone devices.





--
Sent using Dekko from my Ubuntu phone

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Hardware required to use Ubuntu phone as desktop

[Ionut Negru]

Hello,

I wonder if there is anyone that has tried to use the phone with external
keyboard, mouse and display all together. Is mhl support working yet? What
accessories did you use?

I run ubuntu on mx4. Thanks!

Ionut
-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] Hardware required to use Ubuntu phone as desktop

[Ionut Negru]

So far I have tested my dell docking station to handle both mouse and
keyboard via OTG cable and it works nicely. I have tested a MHL cable but
it doesn't seem to work even on a samsung device that is supposed to work
with (it might be defective). The Mx4 Android version is advertised with
MHL support and the hardware is the same as for the ubuntu-touch version.

On Sat, Oct 10, 2015 at 2:02 PM Simos Xenitellis 
wrote:

> On Sat, Oct 10, 2015 at 1:22 PM, Ionut Negru 
> wrote:
>
>> Hello,
>>
>> I wonder if there is anyone that has tried to use the phone with external
>> keyboard, mouse and display all together. Is mhl support working yet?
>> What accessories did you use?
>>
>> I run ubuntu on mx4. Thanks!
>>
>>
> There was a recent discussion about MHL support.
> Meizu does not explicitly mention MHL support for the MX4 (not the MX4
> Pro) on Android.
> Some people asked at http://forum.meizu.com/viewthread.php?tid=17450 with
> no reply.
> What is not conclusive, is whether the MX4 has the full hardware set of
> parts to support MHL.
> The SoC for the MX4 (MediaTek) supports MHL, however the phone needs an
> extra chip that will work
> with the SoC for MHL. It is not clear if it is there.
> If you see
>
> http://www.siliconimage.com/Company/News_and_Events/Press_Releases/2014_02_23_-_Silicon_Image_Announces_New_MHL%C2%AE_Smartphone_Reference_Designs_with_MediaTek/
> it mentions (that's how I interpret it) that a device needs to also have
> the SiI8348 MHL transmitter chip
> to work with the SoC.
> We either get the Meizu tech people to make a statement, or we find some
> high resolution images
> of the MX4 board and then try to identify whether the MHL support chip is
> present on the board.
>
> Regarding keyboard and mouse: there will be an update in the Bluetooth
> software to BlueZ 5.0
> (currently BlueZ 4.0) which will probably allow to use Bluetooth
> peripherals.
> Some Bluetooth devices might work already, however the update to BlueZ 5
> will be substantial.
>
> At the moment you can use an adapter for microUSB to standard USB
> (female),
> which allows to connect all sort of USB devices. Many people use that and
> it works well.
> See for example,
> http://www.amazon.com/Micro-USB-Male-Female-Adapter/dp/B0027YYMU6
> It might make sense to get something like
> http://www.amazon.com/StarTech-com-5in-Micro-Host-Adapter/dp/B00B4GGW5Q/
> so that there would be less chances for an accident that would break the
> MX4 USB port.
>
> Simos
>
-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] Hardware required to use Ubuntu phone as desktop

[Ionut Negru]

PS: this is sad looking forward to have the convergence features

On Sat, Oct 10, 2015 at 2:48 PM Ionut Negru  wrote:

> So far I have tested my dell docking station to handle both mouse and
> keyboard via OTG cable and it works nicely. I have tested a MHL cable but
> it doesn't seem to work even on a samsung device that is supposed to work
> with (it might be defective). The Mx4 Android version is advertised with
> MHL support and the hardware is the same as for the ubuntu-touch version.
>
> On Sat, Oct 10, 2015 at 2:02 PM Simos Xenitellis <
> simos.li...@googlemail.com> wrote:
>
>> On Sat, Oct 10, 2015 at 1:22 PM, Ionut Negru 
>> wrote:
>>
>>> Hello,
>>>
>>> I wonder if there is anyone that has tried to use the phone with external
>>> keyboard, mouse and display all together. Is mhl support working yet?
>>> What accessories did you use?
>>>
>>> I run ubuntu on mx4. Thanks!
>>>
>>>
>> There was a recent discussion about MHL support.
>> Meizu does not explicitly mention MHL support for the MX4 (not the MX4
>> Pro) on Android.
>> Some people asked at http://forum.meizu.com/viewthread.php?tid=17450
>> with no reply.
>> What is not conclusive, is whether the MX4 has the full hardware set of
>> parts to support MHL.
>> The SoC for the MX4 (MediaTek) supports MHL, however the phone needs an
>> extra chip that will work
>> with the SoC for MHL. It is not clear if it is there.
>> If you see
>>
>> http://www.siliconimage.com/Company/News_and_Events/Press_Releases/2014_02_23_-_Silicon_Image_Announces_New_MHL%C2%AE_Smartphone_Reference_Designs_with_MediaTek/
>> it mentions (that's how I interpret it) that a device needs to also have
>> the SiI8348 MHL transmitter chip
>> to work with the SoC.
>> We either get the Meizu tech people to make a statement, or we find some
>> high resolution images
>> of the MX4 board and then try to identify whether the MHL support chip is
>> present on the board.
>>
>> Regarding keyboard and mouse: there will be an update in the Bluetooth
>> software to BlueZ 5.0
>> (currently BlueZ 4.0) which will probably allow to use Bluetooth
>> peripherals.
>> Some Bluetooth devices might work already, however the update to BlueZ 5
>> will be substantial.
>>
>> At the moment you can use an adapter for microUSB to standard USB
>> (female),
>> which allows to connect all sort of USB devices. Many people use that and
>> it works well.
>> See for example,
>> http://www.amazon.com/Micro-USB-Male-Female-Adapter/dp/B0027YYMU6
>> It might make sense to get something like
>> http://www.amazon.com/StarTech-com-5in-Micro-Host-Adapter/dp/B00B4GGW5Q/
>> so that there would be less chances for an accident that would break the
>> MX4 USB port.
>>
>> Simos
>>
>
-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] Convergence (current status for bq devices)

[Ionut Negru]

'Watching out' it's on though, give us some hints please. Where and when to 
watch out 'more'?


On Friday, 6 November 2015 04:34:04 EET, nick luigi eusebio wrote:
All Convergence stuffs will eventually land on all Ubuntu 
Phones and yes including your ( and my ;-) ) bq Aquaris E5 
however, it won't be very much useful on all official Ubuntu 
Phones released so far. First, as you mentioned, both bq phones 
doesn't support external display and even MX4 seems to not 
support it. It's a hardware thing so Canonical can't really do 
something about it. Second, you won't really want to use both 
E4.5 and E5 as a desktop. They're are simply underpowered. 
Bluetooth keyboard and mouse support will surely be implemented 
in the future via OTA. It's been working on my Nexus 7 for 
months actually but I don't know why the phones doesn't. The 
current status of Convergence is pretty much in-progress but 
we're getting there :-)Man, sorry to tell you this sad news. But 
don't worry, as far as I know the next Ubuntu Phone to be 
released will be a convergent-capable one so watch out for it 
;)


  From: Peter Bittner 
 To: ubuntu-phone  
 Sent: Thursday, November 5, 2015 11:58 PM

 Subject: [Ubuntu-phone] Convergence (current status for bq devices)
   
I have difficulties finding out the current status of convergence.


There have been a few videos and photos around on YouTube, Google+,
OMG!Ubuntu, Ubuntu Wiki, but I've found no official roadmap or release
date for an Ubuntu Touch release with convergence features enabled in
general (on any device). Even worse, on OMG!Ubuntu a commenter
mentions having been told by a Canonical representative that
convergence will never be available for bq Aquaris (4.5) devices:
"""
"The guy in charge of phone development at Canonical UK told me
recently that you won't be able to 'converge' your Aquaris. For one
thing the E4.5 isn't able to support MHL. It just doesn't have the
required hardware to run as a desktop."
"""
See below for some sources.

Also, I've just bought a MHL micro USB to HDMI adapter [1], which
works great for attaching USB pen drives, but when I try to attach
either a wireless keyboard and mouse [2], or an external monitor to my
bq Aquaris E5 Ubuntu Edition (latest OTA, 15.04, r6, VEGETEA01A-...)
nothing happens. Attaching a bluetooth mouse [3] to the phone isn't
supported yet either; same for the bluetooth keyboard of my kids' Kano
device. At least on the stock image updated over the air.

So,what is actually true? Will Ubuntu Touch on our devices be capable
to do convergence, say, with the next OTA update? When can we expect
convergence to work for all devices by default? Is there a status page
or roadmap somewhere?

(BTW, just noted that my phone runs 15.04; will the next OTA bring 15.10?)

Peter





--
Sent using Dekko from my Ubuntu phone

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] Not working features in stable OS

[Ionut Negru]

Are those not working OS features equivalent to a car braking system? I
think not :) What are you really upset about?

On Sun, Nov 29, 2015, 15:09 Krzysztof Tataradziński 
wrote:

> 2015-11-28 22:04 GMT+01:00 Gareth France :
>
>> On 28/11/15 20:42, Krzysztof Tataradziński wrote:
>>
>>> Hello,
>>>
>>> Question about placing unfinished/not working features in OS. If we
>>> look in example at Youtube or Soundcloud Scope, there is a login
>>> option, but it doesn't working (for Youtube there is also option to
>>> enable it in System Settings -> Accounts). So why that buttons with
>>> not working login options are there? Maybe better would be to
>>> delete/hide that buttons until there are repaired? Why OTA after OTA
>>> we seeing them? Is it only bothers me viewing things that are not
>>> working (since few OTAs) or that bother anyone else?
>>>
>>> Best regards,
>>> Krzysztof Tataradziński
>>> https://launchpad.net/~ktatar156
>>>
>>> If it bothers you to see rough edges then why purchase a phone with an
>> operating system which is currently most famous for not being finished? We
>> all accepted before purchase that we would be witnessing the development of
>> the finished product.
>>
>>
> Sorry, but I think You miss the point. In my opinion there is problem with
> providing basic features that can be reached by hardware. Lets see at radio
> FM - doesn't work. 4K recording in MX4 (146 days - aging of the bug
> https://bugs.launchpad.net/canonical-devices-system-image/+bug/1471666 )
> that was advertised when selling phone. Also proper resolution of the
> photos - that is also long-aged bug not repaired yet.
> Suppose that Canonical are making cars. There will develop high-end
> electric car. They will told us that for now car can reach 100 km/h in 4.5
> seconds, has range 560 km on one charge and some other cool features. But
> you ask about breaks - why they are not working? You probably will hear: we
> working on that, don't have hard deadline for that, but we must admit that
> in next software update we improve battery charging and implement feature
> that allow car to fly for 30 seconds. But you are thinking - why I need car
> that can charge fast and fly, if it can't even brake? That is analogical
> situation to convergence - we don't have some basic features worked in
> every other phones, but ignoring them, Canonical is implementing some other
> - of course that convergence feature is great and killing other mobile OSes
> - but I don't care of that, if I can't even use radio FM, send files via
> Bluetooth or download file that phone can't open without proper app.
> I think that Canonical is missing something - there are many basic
> features that are not working and should focus on them. Ubuntu has one of
> the most active community in IT world, but I think there is problem with
> using its resources and communication with it.
> I also understand that Canonical has limited resources, but if there is a
> problem with that - ask community what to.
> My proposal is to create crowdfunding campaign and hire someone to work
> with basic bugs/features. If that campaign would appear, it seems to me
> that people will be more than happy, knowing that their money will go to
> provide the basic functionality of their phones.
>
>> --
>> Mailing list: https://launchpad.net/~ubuntu-phone
>> Post to : ubuntu-phone@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~ubuntu-phone
>> More help   : https://help.launchpad.net/ListHelp
>>
> --
> Mailing list: https://launchpad.net/~ubuntu-phone
> Post to : ubuntu-phone@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~ubuntu-phone
> More help   : https://help.launchpad.net/ListHelp
>
-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] Flash light opening on Tagger after OTA-9

[Ionut Negru]

There were a few changes to qtubuntu-camera. I also experienced this flash
issue and also losing the camera view on app switching. I think most of the
issues with the apps are due to changes in "default settings and default
behavior". Probably this will be fixed by app dev.

On Thu, Jan 28, 2016 at 8:37 PM Ivo Xavier  wrote:

> Same here. Bq e4.5
> --
> Ivo Xavier-Ubuntu Portuguese Translators
> 
>
> No dia 28/01/2016, às 17:40, Francisco Pina Martins <
> f.pinamart...@gmail.com> escreveu:
>
> Confirming that I also suffer from the same issue.
>
> On Thursday, 28 January 2016, bogdan  wrote:
> > OTA-9 is a beautifull update. But I have a problem with using TAGGER
> > app. When I need to scan a QR Code and I open the TAGGER app for that,
> > the flash light is opening until I close the app. It's very annoying
> > and the light is makeing the QR CODE to be hard to be read by phone.
> >
> > Does anyone know what can be the cause fro this from the OTA-9 update?
> > What I can understand is that the app is using camera and also the
> > light from the camera, but... I dont want to.
> >
> > I open a bug already here
> > https://bugs.launchpad.net/tagger/+bug/1539087
> > But I listed the problem here, because maybe is a bug about the OTA-9
> > and not about the TAGGER app.
> >
> >
> > --
> > Mailing list: https://launchpad.net/~ubuntu-phone
> > Post to : ubuntu-phone@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~ubuntu-phone
> > More help   : https://help.launchpad.net/ListHelp
> > --
> Mailing list: https://launchpad.net/~ubuntu-phone
> Post to : ubuntu-phone@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~ubuntu-phone
> More help   : https://help.launchpad.net/ListHelp
>
>
> --
> Mailing list: https://launchpad.net/~ubuntu-phone
> Post to : ubuntu-phone@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~ubuntu-phone
> More help   : https://help.launchpad.net/ListHelp
>
-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] new Dekko rocks

[Ionut Negru]

Hi,

Will we see soon a build for desktop?

:)

On Tuesday, 9 February 2016 16:08:47 EET, Ari Börde Kröyer 
 wrote:

Hi

The new Dekko looks great at first, but I have been unable to open my 
emails.


In the listview (inbox) I can mark one and tap the open envelope icon, 
but nothing happens. Am I doing something wrong, or have I encountered a 
bug?


Best regards,
Ari

Den 09. feb. 2016 08:32, skrev Jouni Helminen:
Glad you like the new look and feel, a few other core apps will soon 
be getting a similar UI refresh with the new light design language and 
refreshed visuals.


Huge props to Dan for putting so much time and love into Dekko, and a 
shout out to Faenil for the new fast listitems!


On Sun, Feb 7, 2016 at 8:41 PM, Olivier Tilloy 
mailto:olivier.til...@canonical.com>> 
wrote:


On Sun, Feb 7, 2016 at 11:56 AM, Matthias Apitz mailto:g...@unixarea.de>> wrote:
> I updated yesterday to the new Dekko 0.6 and I'm deeply
impressed by the new
> look&feel and more even functionality. Thank you, Daniel, for
you good work.
> Matthias

I concur, great update, thanks everyone who contributed to it!

 Olivier

--
Mailing list: https://launchpad.net/~ubuntu-phone

Post to : ubuntu-phone@lists.launchpad.net

Unsubscribe : https://launchpad.net/~ubuntu-phone

More help   : https://help.launchpad.net/ListHelp










--
Sent using Dekko from my Ubuntu phone

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] new Dekko rocks

[Ionut Negru]

I was referring to version 0.6 build

On Tue, Feb 9, 2016 at 5:59 PM Mattias de Hollander 
wrote:

> On 02/09/2016 04:32 PM, Ionut Negru wrote:
> > Hi,
> >
> > Will we see soon a build for desktop?
> >
> > :)
> >
> > On Tuesday, 9 February 2016 16:08:47 EET, Ari Börde Kröyer
> >  wrote:
> >> Hi
> >>
> >> The new Dekko looks great at first, but I have been unable to open my
> >> emails.
> >>
> >> In the listview (inbox) I can mark one and tap the open envelope
> >> icon, but nothing happens. Am I doing something wrong, or have I
> >> encountered a bug?
> >>
> >> Best regards,
> >> Ari
> >>
> >> Den 09. feb. 2016 08:32, skrev Jouni Helminen:
> >>> Glad you like the new look and feel, a few other core apps will soon
> >>> be getting a similar UI refresh with the new light design language
> >>> and refreshed visuals.
> >>>
> >>> Huge props to Dan for putting so much time and love into Dekko, and
> >>> a shout out to Faenil for the new fast listitems!
> >>>
> >>> On Sun, Feb 7, 2016 at 8:41 PM, Olivier Tilloy
> >>> mailto:olivier.til...@canonical.com>>
> >>> wrote:
> >>>
> >>> On Sun, Feb 7, 2016 at 11:56 AM, Matthias Apitz  >>> <mailto:g...@unixarea.de>> wrote:
> >>> > I updated yesterday to the new Dekko 0.6 and I'm deeply
> >>> impressed by the new
> >>> > look&feel and more even functionality. Thank you, Daniel, for
> >>> you good work.
> >>> > Matthias
> >>>
> >>> I concur, great update, thanks everyone who contributed to it!
> >>>
> >>>  Olivier
> >>>
> >>> --
> >>> Mailing list: https://launchpad.net/~ubuntu-phone
> >>> <https://launchpad.net/%7Eubuntu-phone>
> >>> Post to : ubuntu-phone@lists.launchpad.net
> >>> <mailto:ubuntu-phone@lists.launchpad.net>
> >>> Unsubscribe : https://launchpad.net/~ubuntu-phone
> >>> <https://launchpad.net/%7Eubuntu-phone>
> >>> More help   : https://help.launchpad.net/ListHelp
> >>>
> >>>
> >>>
> >>>
> >>
> >>
> >
> >
> It is already possible to run Dekko on a desktop computer:
>
> https://websetnet.com/install-dekko-ubuntu-touch-email-client-on-ubuntu-desktops/
>
> --
> Mailing list: https://launchpad.net/~ubuntu-phone
> Post to : ubuntu-phone@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~ubuntu-phone
> More help   : https://help.launchpad.net/ListHelp
>
-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] MX4 preloader

[Ionut Negru]

Hi,

My MX4 Ubuntu edition device died while plugged on USB and I am trying to
resurrect it. Till the event I used the phone without any dev related
activities on it ... it broke before having time to really get into it. It
is so dead that plugging it to USB will not raise any log events at all.

One hint I got was that for some reason emmc got corrupted. Is there anyone
that knows the procedure and managed to successfully rewrite the preloader
for the phone?

PS: I voided the warranty so ANY option is valid.

Thanks!
-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] MX4 preloader

[Ionut Negru]

Hi,

The phone was affected by the "wrong battery stats" bug. In that specific
case I have charged it with the wall charger and it said 100% then 10-15
minutes after it dropped dramatically to about 30% and due to this I
plugged it on my PC till the second day when I found it unresponsive. I
thought that this stats bug could lead to a battery overcharge, if the
charging is also managed by the OS (I know there is an onboard power
management chip handling this as well) ... but I don't know how to check if
this is the real reason.

hi,
> Am Mittwoch, den 29.07.2015, 10:09 +0000 schrieb Ionut Negru:
>
> > My MX4 Ubuntu edition device died while plugged on USB
>
> but you charged it on a wall charger in between, right ? a USB port on a
> PC is definitely not enough (supplying 500mA max while the device is
> attached will pretty much just compensate for what the device uses with
> the screen off, also note that when USB is connected phones usually do
> not suspend so over time it will discharge) ...
>
> my first step would be to attach it to a proper charger for half a day
> before searching for other causes ...
>
> ciao
> oli
>
>
> --
> Mailing list: https://launchpad.net/~ubuntu-phone
> Post to : ubuntu-phone@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~ubuntu-phone
> More help   : https://help.launchpad.net/ListHelp
>
-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] MX4 preloader

[Ionut Negru]

Dear Sebastian,

Thank you very much for the comprehensive response!

My problem is that I can't make any OS (Ubuntu or Windows) to even detect
that I have plugged the phone on to USB.

I have found this video(https://www.youtube.com/watch?v=A3TmXtOA0IA) that
shows how to force a meta boot with a hardware mod using the testpoint pin,
however, it is not working for MX4. Actually I can generate some kind of
USB plug-in event but the OS is not able to communicate with the phone at
all, not even for getting its device description. So it might be just some
bogus voltage variation that gets detected by the OS.

Regards,
Ionut

On Wed, Jul 29, 2015 at 9:19 PM Nolaan  wrote:

>  You can search the mailing list for the thread : [Ubuntu-phone] Flash
> MX4 Ubuntu Edition. Did it work to flash flyme?
>
>
>
> Here's a method Sebastian Hiller posted :
>
>
>
> Hello there,
>
>
>
> i was semi-successful. I did manage to get Flyme working however there are
> major drawbacks which i haven't found a fix for yet (will test over the
> weekend when i have more spare time)
>
> First things first i've tested the I and A versions of Flyme (which should
> definitely work since it is the MX4 M461 Model = international model,
> please check the model on your battery. If it is M460 it is the chinese
> version with locked bootloader and it wont work at all), so versions
> 4.0.4I, 4.2.8.2I and 4.5.3.1A
>
>
>
>
>
> Now the way this works is:
>
> You need adb and fastboot on your machine (tested on OS X, Win 10 and
> 15.04) As far as i can tell OS doesn't matter, there might be a driver
> problem and your MX4 wont be recognized. If that happens check google for
> the MX4 Windows drivers. Also use USB 2.0 Ports, on all of my USB 3.0 Ports
> the Meizu wasn't recognized at all. You'll also need a recovery.img for
> flyme. Any version of that works it is just used to get in the default
> flyme recovery menu (can even be chinese. find it through google or create
> your own if you have a spare Meizuphone lying around)
>
> Now to the fun part: Boot your MX4 into fastboot (Vol down + power)
>
> Connect to PC
>
> Fire up Terminal, CMD or whatever command line you are using.
>
> fastboot -w (this clears the cache and user partitions on your MX4)
>
> fastboot flash recovery recovery.img
>
> shut down your mx4 and boot it in recovery mode (Vol up + power)
>
> Your device should now mount as "recovery" (size around 1GB)
>
> Move update.zip (the flyme update) to the recovery partition
>
> On your phone make sure the first box is checked ("firmware update", might
> also be in chinese so you won't be able to read it, but it is always the
> first one) and hit the blue continue button
>
> Your device will update (even replace the correct recovery partition, that
> is why the first one doesn't matter) and boot into flyme
>
> But then things get strange:
>
>
>
> 4.0.4I will fully work and boot normally (it may take some minutes the
> first time). However graphics are bugged. Colors are missing saturation and
> it appears that the graphics driver or chip is not working with this
> version (laggy like hell, colors seem rendered by cpu) This will also carry
> on to ubuntu if you flash it back. You first have to update to one of the
> following versions and then got to ubuntu if you want correct color
> replication
>
> 4.2.8.2I will be stuck at boot / flyme logo. The device turns hot after a
> few minutes so there must be something wrong with the version (oddly enough
> colors appear fixed) This happens for OTA update as well as native update
> through recovery. Clearing cache and user data doesn't fix that one either
>
> 4.5.3.1A i've managed to get this to work. It might need a few reboots (it
> is stuck at flyme logo too) But there are bugs with the native browser,
> therefore signing in to google play services with 2factor auth. is not
> working as the browser crashes every time. You can chose chrome as a
> default, but for critical tasks it will always use the one that is bundled
> with flyme so you cannot use it as your main phone (at least i can't, might
> be ok for you)
>
>
>
> As you can see it isn't fully working but better than nothing. I think
> there are just some minor corrections needed or maybe i'm missing something.
>
>
>
> Good thing is, the device partitions wont be screwed up (at least if you
> do it this way, if you use flash tools be VERY careful what you do or you
> screw up you whole device) Therefore you can flash ubuntu back at any time.
> Just get the ubuntu recovery.img flash it through fastboot and then plug it
> in to flash ubuntu in the usual manner th

Re: [Ubuntu-phone] MX4 preloader

[Ionut Negru]

I understand you had to ask :). The answer is yes to all the questions. It
is not related chargers or cables. I even checked the microUSB plug of the
phone for dirt or anything that would obstruct the conductivity.

On Thu, Jul 30, 2015 at 5:24 PM Nicholas Skaggs <
nicholas.ska...@canonical.com> wrote:

> On 07/29/2015 04:25 PM, Ionut Negru wrote:
> > Dear Sebastian,
> >
> > Thank you very much for the comprehensive response!
> >
> > My problem is that I can't make any OS (Ubuntu or Windows) to even
> > detect that I have plugged the phone on to USB.
> >
> > I have found this video(https://www.youtube.com/watch?v=A3TmXtOA0IA)
> > that shows how to force a meta boot with a hardware mod using the
> > testpoint pin, however, it is not working for MX4. Actually I can
> > generate some kind of USB plug-in event but the OS is not able to
> > communicate with the phone at all, not even for getting its device
> > description. So it might be just some bogus voltage variation that
> > gets detected by the OS.
> I have to ask; did you try a different cord? A different usb port? A
> short USB cord and trying in USB2 and USB3 ports would be my first stop.
> Granted I assume it all worked before, but :-)
>
>
> Nicholas
>
-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] MX4 preloader

[Ionut Negru]

lsusb does not list the port in question as it does not detect anything on
it

It might be a fried chipset but it is so weird for such a thing to happen
so suddenly. Furthermore, the battery was fully charged after the phone
died (measured voltage 4.2) and this excludes some overheating due to some
looping process/app.

I ordered a replacement battery so I should have it next week to test if
the battery is the problem. However I have some doubts about that being the
malfunctioning reason.

Thanks

On Thu, Jul 30, 2015 at 1:49 PM Nolaan  wrote:

> The MT6595 chip is not yet cracked. It's on the way tho.
>
> What happens when you plug the phone on linux and run lsusb?
>
>
>
> Le mercredi 29 juillet 2015, 20:25:56 Ionut Negru a écrit :
>
> > Dear Sebastian,
>
> >
>
> > Thank you very much for the comprehensive response!
>
> >
>
> > My problem is that I can't make any OS (Ubuntu or Windows) to even detect
>
> > that I have plugged the phone on to USB.
>
> >
>
> > I have found this video(https://www.youtube.com/watch?v=A3TmXtOA0IA)
> that
>
> > shows how to force a meta boot with a hardware mod using the testpoint
> pin,
>
> > however, it is not working for MX4. Actually I can generate some kind of
>
> > USB plug-in event but the OS is not able to communicate with the phone at
>
> > all, not even for getting its device description. So it might be just
> some
>
> > bogus voltage variation that gets detected by the OS.
>
> >
>
> > Regards,
>
> > Ionut
>
> >
>
> > On Wed, Jul 29, 2015 at 9:19 PM Nolaan  wrote:
>
> > > You can search the mailing list for the thread : [Ubuntu-phone] Flash
>
> > >
>
> > > MX4 Ubuntu Edition. Did it work to flash flyme?
>
> > >
>
> > >
>
> > >
>
> > > Here's a method Sebastian Hiller posted :
>
> > >
>
> > >
>
> > >
>
> > > Hello there,
>
> > >
>
> > >
>
> > >
>
> > > i was semi-successful. I did manage to get Flyme working however there
> are
>
> > > major drawbacks which i haven't found a fix for yet (will test over the
>
> > > weekend when i have more spare time)
>
> > >
>
> > > First things first i've tested the I and A versions of Flyme (which
> should
>
> > > definitely work since it is the MX4 M461 Model = international model,
>
> > > please check the model on your battery. If it is M460 it is the chinese
>
> > > version with locked bootloader and it wont work at all), so versions
>
> > > 4.0.4I, 4.2.8.2I and 4.5.3.1A
>
> > >
>
> > >
>
> > >
>
> > >
>
> > >
>
> > > Now the way this works is:
>
> > >
>
> > > You need adb and fastboot on your machine (tested on OS X, Win 10 and
>
> > > 15.04) As far as i can tell OS doesn't matter, there might be a driver
>
> > > problem and your MX4 wont be recognized. If that happens check google
> for
>
> > > the MX4 Windows drivers. Also use USB 2.0 Ports, on all of my USB 3.0
>
> > > Ports
>
> > > the Meizu wasn't recognized at all. You'll also need a recovery.img for
>
> > > flyme. Any version of that works it is just used to get in the default
>
> > > flyme recovery menu (can even be chinese. find it through google or
> create
>
> > > your own if you have a spare Meizuphone lying around)
>
> > >
>
> > > Now to the fun part: Boot your MX4 into fastboot (Vol down + power)
>
> > >
>
> > > Connect to PC
>
> > >
>
> > > Fire up Terminal, CMD or whatever command line you are using.
>
> > >
>
> > > fastboot -w (this clears the cache and user partitions on your MX4)
>
> > >
>
> > > fastboot flash recovery recovery.img
>
> > >
>
> > > shut down your mx4 and boot it in recovery mode (Vol up + power)
>
> > >
>
> > > Your device should now mount as "recovery" (size around 1GB)
>
> > >
>
> > > Move update.zip (the flyme update) to the recovery partition
>
> > >
>
> > > On your phone make sure the first box is checked ("firmware update",
> might
>
> > > also be in chinese so you won't be able to read it, but it is always
> the
>
> > > first one) and hit the blue continue button
>
> > >
>
> > > Your device will update (even replace the correct recovery partitio

Re: [Ubuntu-phone] MX4 preloader

[Ionut Negru]

Evrika! I have managed to figure out the main board testmode procedure,
reflash recovery and reset the Ubuntu OS. I hope it will stay alive from
now on :)

I don't really know what was the cause nor how come clearing cache with
(fastboot -w) and reflashing recovery solved the issue. I did not reflash
the preloader though.

Thank you all for giving me and my problem your precious time!

Regards,
Ionut

On Thu, Jul 30, 2015 at 7:18 PM Ionut Negru  wrote:

> lsusb does not list the port in question as it does not detect anything on
> it
>
> It might be a fried chipset but it is so weird for such a thing to happen
> so suddenly. Furthermore, the battery was fully charged after the phone
> died (measured voltage 4.2) and this excludes some overheating due to some
> looping process/app.
>
> I ordered a replacement battery so I should have it next week to test if
> the battery is the problem. However I have some doubts about that being the
> malfunctioning reason.
>
> Thanks
>
>
> On Thu, Jul 30, 2015 at 1:49 PM Nolaan  wrote:
>
>> The MT6595 chip is not yet cracked. It's on the way tho.
>>
>> What happens when you plug the phone on linux and run lsusb?
>>
>>
>>
>> Le mercredi 29 juillet 2015, 20:25:56 Ionut Negru a écrit :
>>
>> > Dear Sebastian,
>>
>> >
>>
>> > Thank you very much for the comprehensive response!
>>
>> >
>>
>> > My problem is that I can't make any OS (Ubuntu or Windows) to even
>> detect
>>
>> > that I have plugged the phone on to USB.
>>
>> >
>>
>> > I have found this video(https://www.youtube.com/watch?v=A3TmXtOA0IA)
>> that
>>
>> > shows how to force a meta boot with a hardware mod using the testpoint
>> pin,
>>
>> > however, it is not working for MX4. Actually I can generate some kind of
>>
>> > USB plug-in event but the OS is not able to communicate with the phone
>> at
>>
>> > all, not even for getting its device description. So it might be just
>> some
>>
>> > bogus voltage variation that gets detected by the OS.
>>
>> >
>>
>> > Regards,
>>
>> > Ionut
>>
>> >
>>
>> > On Wed, Jul 29, 2015 at 9:19 PM Nolaan  wrote:
>>
>> > > You can search the mailing list for the thread : [Ubuntu-phone] Flash
>>
>> > >
>>
>> > > MX4 Ubuntu Edition. Did it work to flash flyme?
>>
>> > >
>>
>> > >
>>
>> > >
>>
>> > > Here's a method Sebastian Hiller posted :
>>
>> > >
>>
>> > >
>>
>> > >
>>
>> > > Hello there,
>>
>> > >
>>
>> > >
>>
>> > >
>>
>> > > i was semi-successful. I did manage to get Flyme working however
>> there are
>>
>> > > major drawbacks which i haven't found a fix for yet (will test over
>> the
>>
>> > > weekend when i have more spare time)
>>
>> > >
>>
>> > > First things first i've tested the I and A versions of Flyme (which
>> should
>>
>> > > definitely work since it is the MX4 M461 Model = international model,
>>
>> > > please check the model on your battery. If it is M460 it is the
>> chinese
>>
>> > > version with locked bootloader and it wont work at all), so versions
>>
>> > > 4.0.4I, 4.2.8.2I and 4.5.3.1A
>>
>> > >
>>
>> > >
>>
>> > >
>>
>> > >
>>
>> > >
>>
>> > > Now the way this works is:
>>
>> > >
>>
>> > > You need adb and fastboot on your machine (tested on OS X, Win 10 and
>>
>> > > 15.04) As far as i can tell OS doesn't matter, there might be a driver
>>
>> > > problem and your MX4 wont be recognized. If that happens check google
>> for
>>
>> > > the MX4 Windows drivers. Also use USB 2.0 Ports, on all of my USB 3.0
>>
>> > > Ports
>>
>> > > the Meizu wasn't recognized at all. You'll also need a recovery.img
>> for
>>
>> > > flyme. Any version of that works it is just used to get in the default
>>
>> > > flyme recovery menu (can even be chinese. find it through google or
>> create
>>
>> > > your own if you have a spare Meizuphone lying around)
>>
>> > >
>>
>> > > Now to the fun part

Re: [Ubuntu-phone] MX4 preloader

[Ionut Negru]

PS: I realise now that this might be a software related issue after all :S.
What could have caused this if I have used the MX4 before the incident only
as a normal user not as a developer?

On Fri, Jul 31, 2015 at 7:58 PM Ionut Negru  wrote:

> Evrika! I have managed to figure out the main board testmode procedure,
> reflash recovery and reset the Ubuntu OS. I hope it will stay alive from
> now on :)
>
> I don't really know what was the cause nor how come clearing cache with
> (fastboot -w) and reflashing recovery solved the issue. I did not reflash
> the preloader though.
>
> Thank you all for giving me and my problem your precious time!
>
> Regards,
> Ionut
>
>
> On Thu, Jul 30, 2015 at 7:18 PM Ionut Negru  wrote:
>
>> lsusb does not list the port in question as it does not detect anything
>> on it
>>
>> It might be a fried chipset but it is so weird for such a thing to happen
>> so suddenly. Furthermore, the battery was fully charged after the phone
>> died (measured voltage 4.2) and this excludes some overheating due to some
>> looping process/app.
>>
>> I ordered a replacement battery so I should have it next week to test if
>> the battery is the problem. However I have some doubts about that being the
>> malfunctioning reason.
>>
>> Thanks
>>
>>
>> On Thu, Jul 30, 2015 at 1:49 PM Nolaan  wrote:
>>
>>> The MT6595 chip is not yet cracked. It's on the way tho.
>>>
>>> What happens when you plug the phone on linux and run lsusb?
>>>
>>>
>>>
>>> Le mercredi 29 juillet 2015, 20:25:56 Ionut Negru a écrit :
>>>
>>> > Dear Sebastian,
>>>
>>> >
>>>
>>> > Thank you very much for the comprehensive response!
>>>
>>> >
>>>
>>> > My problem is that I can't make any OS (Ubuntu or Windows) to even
>>> detect
>>>
>>> > that I have plugged the phone on to USB.
>>>
>>> >
>>>
>>> > I have found this video(https://www.youtube.com/watch?v=A3TmXtOA0IA)
>>> that
>>>
>>> > shows how to force a meta boot with a hardware mod using the testpoint
>>> pin,
>>>
>>> > however, it is not working for MX4. Actually I can generate some kind
>>> of
>>>
>>> > USB plug-in event but the OS is not able to communicate with the phone
>>> at
>>>
>>> > all, not even for getting its device description. So it might be just
>>> some
>>>
>>> > bogus voltage variation that gets detected by the OS.
>>>
>>> >
>>>
>>> > Regards,
>>>
>>> > Ionut
>>>
>>> >
>>>
>>> > On Wed, Jul 29, 2015 at 9:19 PM Nolaan  wrote:
>>>
>>> > > You can search the mailing list for the thread : [Ubuntu-phone] Flash
>>>
>>> > >
>>>
>>> > > MX4 Ubuntu Edition. Did it work to flash flyme?
>>>
>>> > >
>>>
>>> > >
>>>
>>> > >
>>>
>>> > > Here's a method Sebastian Hiller posted :
>>>
>>> > >
>>>
>>> > >
>>>
>>> > >
>>>
>>> > > Hello there,
>>>
>>> > >
>>>
>>> > >
>>>
>>> > >
>>>
>>> > > i was semi-successful. I did manage to get Flyme working however
>>> there are
>>>
>>> > > major drawbacks which i haven't found a fix for yet (will test over
>>> the
>>>
>>> > > weekend when i have more spare time)
>>>
>>> > >
>>>
>>> > > First things first i've tested the I and A versions of Flyme (which
>>> should
>>>
>>> > > definitely work since it is the MX4 M461 Model = international model,
>>>
>>> > > please check the model on your battery. If it is M460 it is the
>>> chinese
>>>
>>> > > version with locked bootloader and it wont work at all), so versions
>>>
>>> > > 4.0.4I, 4.2.8.2I and 4.5.3.1A
>>>
>>> > >
>>>
>>> > >
>>>
>>> > >
>>>
>>> > >
>>>
>>> > >
>>>
>>> > > Now the way this works is:
>>>
>>> > >
>>>
>>> > > You need adb and fastboot on your machine (