ahmed_sam has quit [Ping timeout: 258 seconds]
noidea_ has quit [Remote host closed the connection]
noidea_ has joined #maemo-leste
sch has joined #maemo-leste
k1r1t0 has quit [Ping timeout: 255 seconds]
<Wizzup> freemangordon: hm, well, the tracker indexed my stuf and then removed itall again
xmn has joined #maemo-leste
ahmed_sam has joined #maemo-leste
<freemangordon> Wizzup: no idea
<freemangordon> maybe check the status
<freemangordon> or runt tracker-extract from the shell
joerg has quit [Ping timeout: 255 seconds]
joerg has joined #maemo-leste
ahmed_sam has quit [Read error: Connection reset by peer]
xmn has quit [Ping timeout: 260 seconds]
parazyd has joined #maemo-leste
<Wizzup> freemangordon: now it's ok again
<Wizzup> oh, no, empty again :D
<Wizzup> I will tell it not to recurse home
<Wizzup> maybe this makes it unhappy
<freemangordon> Wizzup: better try to find what happens
<freemangordon> like, maybe attach gdb or run it manually with -v3
<freemangordon> and G_MESSAGES_DEBUG-all
<freemangordon> *=all
<Wizzup> I don't even know if it crashes though
<Wizzup> I guess I need to stop it all first, and then what?
<Wizzup> df -h
<Wizzup> oops
<Wizzup> yeah, same thing, it seems
<Wizzup> maybe somehow starting omp / mafw-tracker-source made it drop all its entries
<freemangordon> ok, stop mafw-tracker-source and then reset
<freemangordon> /usr/bin/mafw.sh stop mafw-tracker-source
<Wizzup> so stop with dsmetool, then tracker reset --hard, then G_MESSAGES_DEBUG=all /usr/libexec/tracker-miner-fs -n -v 3
<Wizzup> and then /usr/bin/mafw.sh start mafw-tracker-source
<Wizzup> (after a bit)
<freemangordon> no
<freemangordon> stop mafw, reset db, start mafw
<freemangordon> lets see if it will recover
<freemangordon> if not, then we'll see what to do
<Wizzup> so it will start the tracker?
<freemangordon> yes
<Wizzup> I doubt it will since I've done this many times throug reboot, but will try
<Wizzup> how tracker actually mines is a mystery to me too
<freemangordon> maybe I'll have to change tracker source to not keep permanent connection to the tracker
<freemangordon> as this seems to keep sqlite db opened
<freemangordon> and tracker reset *deletes* the db
<freemangordon> and it becomes a mess
<Wizzup> ok
<Wizzup> it's running again
<freemangordon> wild guess, but that's what I suppose happens
<Wizzup> what's kind of weird is that tracker finds some files immediately, but the rest it will index much later or something
<freemangordon> we have miners and then extract
<freemangordon> those run in separate "passes"
<Wizzup> ok
<Wizzup> well it's doing something now, so I'll wait
<Wizzup> whatever it did, it's back to very few files again
<Wizzup> tracker search -m | wc -l
<Wizzup> this was 500+ just minutes ago
<Wizzup> (2 means 0)
<Wizzup> now stopping mafw and trying to see if it doesn't go down
<freemangordon> something is crashing it
<Wizzup> but the tracker processes themselves don't seem to crash
<Wizzup> like, it's not like their start time changes
<freemangordon> hmm
<Wizzup> afaict
<freemangordon> no idea then
<freemangordon> actually
<freemangordon> try one more h
<freemangordon> thing:
<freemangordon> stop mafw, reset the tracker and delete /home/user/.cache/tracker/
<Wizzup> ok, even with mafw-tracker-source not running it does the same thing
<Wizzup> (tracker-miner-fs:11224): Tracker-DEBUG: 16:21:40.959: tracker-extract vanished, maybe restarting.
<Wizzup> hm
<freemangordon> riht
<freemangordon> *right
<freemangordon> do tracker daemon -t
<Wizzup> ok, they are terminated
<freemangordon> and then G_MESSAGES_DEBUG=all /usr/libexec/tracker-extract -v3
<Wizzup> -v 3
<Wizzup> but yes
<freemangordon> yeah
<freemangordon> my kbd misbehaves somethimes
<Wizzup> it just stops after inactivity
<freemangordon> ok, delete the databes folder
<Wizzup> should it run while miner is running?
<Wizzup> seems like it
<freemangordon> *database
<freemangordon> rm -fr /home/user/.cache/tracker/
<Wizzup> it's running atm, should I stop it?
<Wizzup> if it's going to crash this might trigger it too
<freemangordon> stop it then
<freemangordon> and the delete the db
<Wizzup> ok
<Wizzup> and then only start extract
<Wizzup> ?
<freemangordon> and then tracker daemon -s
<freemangordon> if that does not wok, later on I will request remote shell :)
<Wizzup> ok
<Wizzup> it's running atm
<Wizzup> it just stops by itself after there is no more to do, no crash
<freemangordon> is it ok now?
<Wizzup> currently, yes, but it's been like this before
<Wizzup> I will leave it like this fo a bit before I start mafw
<freemangordon> ok, start mafw
<freemangordon> have to run, bbl
<Wizzup> currently it looks ok
<Wizzup> let's see if it continues
pere has joined #maemo-leste
akossh has joined #maemo-leste
<Wizzup> still fine currently
<Wizzup> still stable, will reboot and see what happens
xmn has joined #maemo-leste
<Wizzup> uvos: tmlind: so the trick is to just install kexecboot and then one can boot to stock android and/or the sdcard, right?
<Wizzup> do we need a certain android version?
* Wizzup should re-read the logs from like last year
pere has quit [Ping timeout: 248 seconds]
<sicelo> anyone on N900, i'm curious to see what you get from `busctl call org.ofono /n900_0 org.ofono.NetworkRegistration GetProperties`
<sicelo> you could mask off the lac and cid if necessary
<sicelo> seems to me N900 does not report operator name, at least not in a 'normal
<sicelo> way
<sicelo> it's not critical, of course, since, after doing a scan, you can get operator name from the /n900_0/operator/xxxxx path, but i'm still curious nonetheless
<sicelo> and would like to fix it at some point, since actually the operator name is constantly being sent to ofono by the modem
fab_ has joined #maemo-leste
fab_ has quit [Ping timeout: 252 seconds]
pere has joined #maemo-leste
_whitelogger has joined #maemo-leste
<sicelo> ah, this happens only on some operators ... on a different sim, operator name is filled in perfectly ootb
ahmed_sam has joined #maemo-leste
ahmed_sam has quit [Read error: Connection reset by peer]
pere has quit [Ping timeout: 255 seconds]
uvos has joined #maemo-leste
<uvos> Wizzup: you install kexecboot on androids cache partition
<uvos> android still sortof works after that, but its wonky
<uvos> mostly you can still use it for charging, wich is important because the mianline kernel and bearly charge the device
<uvos> as it has a extra charging chip for that that is currently not supported
<uvos> and cpcap cant really keep up with the tablets bigger power draw, nor can it really put a dent into the huge battery in resonable timespans
<uvos> mz617 has no sdcard reader
<uvos> you can install an extreamly limited rootfs without breaking android further
<uvos> realistcly you need to overwrite at least the exdata partiton, causeing even more issues for android
<uvos> unfortinatly because of the power and storage issues, its quite easy to end up in at least a soft brick
<uvos> i frankly dont see a resonable user frendly way to install leste on mz617 for now
<uvos> mz609 is more frendly to our purposes
<uvos> some of the european versions also have a sdcard reader, im not quite sure which however
<uvos> but they have no modem so, you lose that then
kona has left #maemo-leste [#maemo-leste]
TheTechRobo has joined #maemo-leste
pere has joined #maemo-leste
ahmed_sam has joined #maemo-leste
ahmed_sam has quit [Read error: Connection reset by peer]
akossh has quit [Quit: Leaving.]