Jump to content

fixed: On Ubuntu Touch Meizu MX4 for AIDA64 is android lollipop


Recommended Posts

Yes, it's because Ubuntu Touch devices feature several portions of Android actually ;) The reported Android version is not the OS version, but the Android subsystem version. Here's how the Ubuntu Touch architecture looks like:

ubuntu_touch_architecture.png

Ubuntu Touch OS version cannot be detected due to platform issues about too strict sandboxing (confinement) solution called Ubuntu AppArmor. AppArmor prevents not only regular apps to detect certain system details like Ubuntu Touch OS version, battery readouts and temperature measurement, but also cripples built-in Qt5 APIs that would otherwise be able to provide some of those details. For example:

* Ubuntu Desktop / 16.04 LTS (latest updates)

QSysInfo::productType(): "ubuntu"

QSysInfo::productVersion(): "16.04"

QSysInfo::prettyProductName(): "Ubuntu 16.04 LTS"

That one was an unconfined environment where everything worked out fine.

But, if you call the same Qt5 APIs on a phone where AppArmor confinement is enforced, you get the following values:

* bq Aquaris E5 HD Ubuntu Edition / 15.04 (OTA-11) / Device Image Part 20160524-63b1875

QSysInfo::productType(): "unknown"

QSysInfo::productVersion(): "unknown"

QSysInfo::prettyProductName(): "Linux 3.4.67"

This is an oversight on Canonical's part, but we've already notified them about this issue. Once they fix it up, our app will be able to report Ubuntu Touch OS version on the OS page. I wouldn't expect that to happen before OTA-14 though, so this fall the earliest.

Regards,

Fiery

Link to comment
Share on other sites

We've just found a workaround for the Ubuntu Touch OS version detection issue. Also, we've renamed the "Android Version" line to "Android Subsystem Version" to avoid further confusion. The AIDA64 for Ubuntu Touch app has already been updated in the Ubuntu Store as v1.0.1.

Link to comment
Share on other sites

  • 7 months later...
On ‎23‎.‎07‎.‎2016 at 9:57 AM, Fiery said:

Yes, it's because Ubuntu Touch devices feature several portions of Android actually ;) The reported Android version is not the OS version, but the Android subsystem version. Here's how the Ubuntu Touch architecture looks like:

ubuntu_touch_architecture.png

Ubuntu Touch OS version cannot be detected due to platform issues about too strict sandboxing (confinement) solution called Ubuntu AppArmor. AppArmor prevents not only regular apps to detect certain system details like Ubuntu Touch OS version, battery readouts and temperature measurement, but also cripples built-in Qt5 APIs that would otherwise be able to provide some of those details. For example:

* Ubuntu Desktop / 16.04 LTS (latest updates)

QSysInfo::productType(): "ubuntu"

QSysInfo::productVersion(): "16.04"

QSysInfo::prettyProductName(): "Ubuntu 16.04 LTS"

That one was an unconfined environment where everything worked out fine.

But, if you call the same Qt5 APIs on a phone where AppArmor confinement is enforced, you get the following values:

* bq Aquaris E5 HD Ubuntu Edition / 15.04 (OTA-11) / Device Image Part 20160524-63b1875

QSysInfo::productType(): "unknown"

QSysInfo::productVersion(): "unknown"

QSysInfo::prettyProductName(): "Linux 3.4.67"

This is an oversight on Canonical's part, but we've already notified them about this issue. Once they fix it up, our app will be able to report Ubuntu Touch OS version on the OS page. I wouldn't expect that to happen before OTA-14 though, so this fall the earliest.

Regards,

Fiery

 

On ‎23‎.‎07‎.‎2016 at 9:14 AM, EmanueleFaraone said:

On Ubuntu Touch Meizu MX4 for AIDA64 is reported android lollipop

 

On ‎23‎.‎07‎.‎2016 at 9:57 AM, Fiery said:

Yes, it's because Ubuntu Touch devices feature several portions of Android actually ;) The reported Android version is not the OS version, but the Android subsystem version. Here's how the Ubuntu Touch architecture looks like:

ubuntu_touch_architecture.png

Ubuntu Touch OS version cannot be detected due to platform issues about too strict sandboxing (confinement) solution called Ubuntu AppArmor. AppArmor prevents not only regular apps to detect certain system details like Ubuntu Touch OS version, battery readouts and temperature measurement, but also cripples built-in Qt5 APIs that would otherwise be able to provide some of those details. For example:

* Ubuntu Desktop / 16.04 LTS (latest updates)

QSysInfo::productType(): "ubuntu"

QSysInfo::productVersion(): "16.04"

QSysInfo::prettyProductName(): "Ubuntu 16.04 LTS"

That one was an unconfined environment where everything worked out fine.

But, if you call the same Qt5 APIs on a phone where AppArmor confinement is enforced, you get the following values:

* bq Aquaris E5 HD Ubuntu Edition / 15.04 (OTA-11) / Device Image Part 20160524-63b1875

QSysInfo::productType(): "unknown"

QSysInfo::productVersion(): "unknown"

QSysInfo::prettyProductName(): "Linux 3.4.67"

This is an oversight on Canonical's part, but we've already notified them about this issue. Once they fix it up, our app will be able to report Ubuntu Touch OS version on the OS page. I wouldn't expect that to happen before OTA-14 though, so this fall the earliest.

Regards,

Fiery

 

On ‎25‎.‎07‎.‎2016 at 8:09 AM, EmanueleFaraone said:

Thanks all!

thx

 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.



×
×
  • Create New...