* Matthias Apitz, g...@unixarea.de [11/01/17 08:28]:
> El d?a Wednesday, January 11, 2017 a las 08:02:14AM +0100, Walter
> Garcia-Fontes escribi?:
>
> > * Wilfridd, wid...@gmail.com [11/01/17 07:31]:
> > > Silly suggestion : the internal speaker might be dead...?
> >
> > Not silly at all, it cou
El d�a Wednesday, January 11, 2017 a las 08:02:14AM +0100, Walter Garcia-Fontes
escribi�:
> * Wilfridd, wid...@gmail.com [11/01/17 07:31]:
> > Silly suggestion : the internal speaker might be dead...?
>
> Not silly at all, it could be. I read reports on internet on the BQ E5
> having a very loos
* Wilfridd, wid...@gmail.com [11/01/17 07:31]:
> Silly suggestion : the internal speaker might be dead...?
Not silly at all, it could be. I read reports on internet on the BQ E5
having a very loose connection to the speakers that gets disconnected
when the device falls and gets hit. I don't rememb
Hi Walter,
Silly suggestion : the internal speaker might be dead...?
Wilfrid
On Tuesday, 10 January 2017 20:46:08 CET, simone allegri
wrote:
Hi folks any news from our speakers? In my e5 still not work...
Il lunedì 9 gennaio 2017, Cesar Herrera ha scritto:
I don't know if this is related
Pat,
Thanks for your valuable teply. I manged to find this workaround.
1. Stop *trust-stoted service
2. Rename *trust.db as backup
3. Reboot he phone, then at this step, all perms have been reset
4. Launch app that required permission to cam, mic(pulse), loc
5. To avoid random crash, select "do
+1
On 10/01/17 20:41, Yann Suire wrote:
I think this is only the consequence of not having anyone from
Canonical expressing what was planned. When you let others communicate
for you, you have to expect some backfire.
Sent from AOL Mobile Mail
I think this is only the consequence of not having anyone from Canonical
expressing what was planned. When you let others communicate for you, you have
to expect some backfire.
Sent from AOL Mobile Mail
On mardi, 10 janvier, 2017 A. James Lewis wrote:
The mails never actually said that there
Hi folks any news from our speakers? In my e5 still not work...
Il lunedì 9 gennaio 2017, Cesar Herrera ha scritto:
> I don't know if this is related to my problem when I receive a call with
E4.5 paired to a Citroen C4 and sound is off.
> Cheers,
> Cesar
>
> 06.01.2017, 21:01, "Walter Garcia-Font
The mails never actually said that there would not be an OTA-15, and the
fact that the system is not snap based does not stop the development of
Unity8 etc... so there is still a chance seeing another few updates,
before the snap migration
Also the Android layer may yet get updated. I th
On 10/01/17 12:17, Paul Tait wrote:
I appreciate what you're saying, but that is the information that I've
gleaned from here.
Yes I agree entirely. But I suspect that the exact wording can be
provocative. Some people like to find the fire even if there is no smoke!
--
Mailing list: https://l
There are several sqlite3 trust databases you can find with
find /home/phablet -name trust.db
You can manually modify them or remove them. I would first stop any related
services:
initctl list | grep trust
for example
stop pulseaudio-trust-stored
rm ./.local/share/PulseAudio/trust.db
start pulseaud
I appreciate what you're saying, but that is the information that I've
gleaned from here.
With no official word from Canonical I suppose we're all just guessing but
from what I've read the E4.5 (which I have too) won't support the snap
based image. And I understood it to be security fixes only
Kirk
I too have a Meizu Pro 5
The Pro 5, I understand, runs the A57, A53 chips,
"The ARM® Cortex®-A57 was the first
high-performance ARMv8-A processor. It extends the reach of the
ARM architecture into premium 64-bit mobile and infrastructure
applications"
Kirk
I too have a Meizu Pro 5
The Pro 5, I understand, runs the A57, A53 chips,
"The ARM Cortex-A57 was the first high-performance ARMv8-A processor. It
extends the reach of the ARM architecture into premium 64-bit mobile and
infrastructure applications"
Which seems to me to indicate the Pr
Hello! I would like to port Ubuntu Touch for my device, but ot seems
like porting instruction is wrong,
When I try to obtin all repos with phablet-dev-bootstrap, I get a message:
Get git://phablet.ubuntu.com/CyanogenMod/android.git
fatal: remote error: access denied or repository not exported:
/Cya
Hey!
With the switch to snaps we also made a decision to switch our target
architecture from armhf to arm64, which is another big complication
for some of our existing phones on the market. For now we are focusing
all our touch efforts on the M10 platform family.
Cheers,
On 10 January 2017 at 0
Thanks for that page - I couldn't find it in my searching.
It certainly shows a range of kernel versions depending on the underlying
OS - and the TBD for Android is I guess the point of contention :)
I'm guessing the minimum of 4.4 for Ubuntu requirement is because of the
live kernel updates that
17 matches
Mail list logo
