<missMyN900>
downloading Devuan Beowulf i386 right now
<missMyN900>
I will try it on the Atom tablet tomorrow
<missMyN900>
by the way, I did some more research and these Atom tablets may not be such good dev devices after all
<missMyN900>
apparently all these Silvermont-based CPUs are affected by the SD/eMMC/USB degradation issue
<missMyN900>
which is an especially big problem for these tablets as they boot from the eMMC (or perhaps a microSD)
<missMyN900>
I have not found any evidence of it specifically affecting these Z-series but it affects the C-series as well as N and J series so I see no reason why these Z-series CPUs would not be affected
<missMyN900>
when they are from the same era and also Silvermont-based
<missMyN900>
by the way I have read the logs from yesterday
<missMyN900>
also updated my PP to the new kernel
<missMyN900>
actually I think standby battery drain may be less
<missMyN900>
rafael2k: I was actually talking about VoLTE on the DB since I may get one
<missMyN900>
I no longer have a SIM in my PP
<missMyN900>
had to cut some expenses
Daanct12 has joined #maemo-leste
Daanct12 has quit [Ping timeout: 276 seconds]
Daanct12 has joined #maemo-leste
missMyN900 has quit [Ping timeout: 248 seconds]
Daaanct12 has joined #maemo-leste
Daanct12 has quit [Ping timeout: 268 seconds]
Daaanct12 has quit [Ping timeout: 240 seconds]
vgratian has left #maemo-leste [#maemo-leste]
vgratian has joined #maemo-leste
norly has quit [Quit: Leaving.]
norly has joined #maemo-leste
joerg has quit [Ping timeout: 240 seconds]
joerg has joined #maemo-leste
Daanct12 has joined #maemo-leste
ikmaak has quit [Quit: No Ping reply in 180 seconds.]
ikmaak has joined #maemo-leste
Daanct12 has quit [Read error: Connection reset by peer]
Daanct12 has joined #maemo-leste
Daaanct12 has joined #maemo-leste
Daanct12 has quit [Ping timeout: 240 seconds]
Daanct12 has joined #maemo-leste
Daaanct12 has quit [Read error: Connection reset by peer]
mardy has joined #maemo-leste
joerg has quit [Ping timeout: 246 seconds]
joerg has joined #maemo-leste
Daaanct12 has joined #maemo-leste
Daanct12 has quit [Ping timeout: 272 seconds]
Daanct12 has joined #maemo-leste
Daaanct12 has quit [Read error: Connection reset by peer]
Daanct12 has quit [Ping timeout: 268 seconds]
ceene has joined #maemo-leste
missMyN900 has joined #maemo-leste
missMyN900 has quit [Ping timeout: 272 seconds]
Twig has joined #maemo-leste
uvos__ has joined #maemo-leste
<uvos__>
missMyN900: you have to install 64bit devuan
<uvos__>
which your cpu supports
<uvos__>
idk how to work around 32bit efi
<uvos__>
but its possible
norayr has quit [Ping timeout: 256 seconds]
vgratian has quit [Ping timeout: 246 seconds]
Daanct12 has joined #maemo-leste
<rafael2k>
missMyN900: good to hear about better battery life in stand-by! Did not know about DB...
Daanct12 has quit [Ping timeout: 246 seconds]
xmn has quit [Ping timeout: 264 seconds]
Daanct12 has joined #maemo-leste
mrkrisprolls has quit [Remote host closed the connection]
mardy has quit [Quit: WeeChat 2.8]
Daanct12 has quit [Ping timeout: 240 seconds]
mardy has joined #maemo-leste
Daanct12 has joined #maemo-leste
ceene has quit [Ping timeout: 240 seconds]
Pali has joined #maemo-leste
Pali has quit [Ping timeout: 272 seconds]
Pali has joined #maemo-leste
Daaanct12 has joined #maemo-leste
Daanct12 has quit [Ping timeout: 272 seconds]
vgratian has joined #maemo-leste
mrkrisprolls has joined #maemo-leste
Guest9053 has joined #maemo-leste
ceene has joined #maemo-leste
<Guest9053>
can anyone kindly tell the use of secure mode from powerkey menu?
<dsc_>
now, not being able to search within messages is not the end of the world HOWEVER what is also upcoming is the searching of "CONTACTS" (names and/or number(s))
<dsc_>
and ideally you'd have search functionaltiy where results are progressively updated as you type
Twig has quit [Ping timeout: 264 seconds]
<dsc_>
actually... I can solve this by doing a broad SELECT, looping over everything, and doing the post-processing (searching) in C++
<dsc_>
not great, but, we are iterating over the results, and not fetching them all at once into memory, so I think that could work just fine
<rafael2k>
what mapphone is?
<rafael2k>
I see some mentions to it in the git repos
Twig has joined #maemo-leste
belcher has quit [Quit: Leaving]
<sicelo>
rafael2k: the supported motorolas
missMyN900 has joined #maemo-leste
<buZz>
sicelo: map = omap ;)
Twig has quit [Remote host closed the connection]
pere has joined #maemo-leste
mardy has quit [Quit: WeeChat 2.8]
<missMyN900>
uvos__: is i386 not supported by ML?
<sicelo>
I believe I already mentioned there's nothing built for i386. I don't recall if there was a more technical reason for that
missMyN900 has quit [Ping timeout: 255 seconds]
uvos has joined #maemo-leste
<uvos>
buZz: im pretty sure the map in mapphone acutally refers to the usage of the "signal map" instead of device tree to define how hardware devices are conected
<uvos>
we dont build for i386 there is no reason for this besides resources.
<sicelo>
Heh, of course N900 isn't a mapphone. I thought map = omap was a joke
<buZz>
ah :)
<buZz>
right, make -j1 of the current kernel on droid 4 = 358 minutes
<uvos>
why j1?
* buZz
considering doing make clean ; time make -j2
<uvos>
also why do it on d4 at all
<uvos>
since kernel is trivial to cross compile
<buZz>
uvos: i imagined it would run out of ram & swap without
<uvos>
buZz: ok
<buZz>
i left full maemo running
<buZz>
also, make -j1 was already taking both cores to 100% ?
<buZz>
maybe because of the SD card
<uvos>
hmm wierd
uvos has quit [Ping timeout: 268 seconds]
Pali has quit [Ping timeout: 256 seconds]
norayr has joined #maemo-leste
<norayr>
folks i think i found a problem
<norayr>
in /usr/include/dbus-1.0/dbus/dbus.h on line 29 it is included:
<norayr>
#include <dbus/dbus-arch-deps.h>
<norayr>
which doesn't exist.
missMyN900 has joined #maemo-leste
<missMyN900>
sicelo: yes, you mentioned that there are no images for x86. However, apparently there are packages being built for the ML repos for x86 architectures. So my question is are those only for 64 bit (AMD64) or also i386 (really i686)?