<Wizzup>
yifei1: I'll see if I can start my pinephonepro tomorrow
<Wizzup>
I should have the tar somewhere
<Wizzup>
iirc the remaining problem was that the hdmi port was being seen as connected and somehow used as output/display
akossh has quit [Quit: Leaving.]
akossh has joined #maemo-leste
ungeskriptet3 has joined #maemo-leste
ungeskriptet has quit [Ping timeout: 256 seconds]
ungeskriptet3 is now known as ungeskriptet
akossh has quit [Remote host closed the connection]
akossh has joined #maemo-leste
akossh has quit [Client Quit]
diejuse has joined #maemo-leste
akossh has joined #maemo-leste
akossh has quit [Client Quit]
akossh has joined #maemo-leste
akossh has quit [Ping timeout: 245 seconds]
diejuse has quit [Ping timeout: 250 seconds]
f_ has quit [Quit: To contact me, send a memo using MemoServ, PM f_[xmpp], or send an email. See https://vitali64.duckdns.org/.]
fab_ has quit [Quit: fab_]
Juesto has joined #maemo-leste
joerg is now known as DocScrutinizer
Juest has quit [Ping timeout: 255 seconds]
Juesto is now known as Juest
DocScrutinizer is now known as joerg
<_Gary>
lost ability to do SMS and reply to SMS
<_Gary>
both sphone new SMS and SMS history crash when trying to open
<_Gary>
i can bring up the conversations SMS and see the message but unable to reply cannot type into the message field
<_Gary>
keyboard does not activate, on a pinephone
<_Gary>
deb leste chimaera-devel main contrib non-free lima pinephone
<_Gary>
recently did a update and upgrade
<Wizzup>
I'll see if I can figure out tomorrow why the rtcom db reset would be necessary for conversations/ring to work
<Wizzup>
I don't know why sphone would crash though, but it's currently known that tp-ring + conversations somehow doesn't work with older sphone rtcom db, even though nothing changed in the format
<Wizzup>
I think it probably messes up the group by statement in conversations because sphone doesn't log that according to fremantle spec in its internal logging
<Wizzup>
s/messes/messed/
<_Gary>
okay many thanks for looking into this
<Wizzup>
for now I think you can 'fix' it by moving the rtcom-el-v1.db elsewhere
<Wizzup>
and then restarting
<_Gary>
I'll give that a try, thanks
diejuse has joined #maemo-leste
<dsc_>
for Qt7 they ought to nuke how tables work imo
<dsc_>
needs a much simpler API
<dsc_>
99% of the times you just want to display some data and not care about roles and whatever else insane boilerplate you need to do when working with tables :P
retr0id8 has joined #maemo-leste
retr0id has quit [Read error: Connection reset by peer]
retr0id8 is now known as retr0id
<dsc_>
"oh you want to insert a row? First use beginInsertRows(), then find out the index where you want to insert it (QModelIndex is akward), oh wait beforehand you need to know how many rows you'll be inserting, then maybe call ->invalidate() on the TableProxy, or not, who knows
<dsc_>
perhaps the author tried his best to make it as confusing as possible. only logical conclusion I have
System_Error has quit [Remote host closed the connection]
xmn has joined #maemo-leste
System_Error has joined #maemo-leste
<Wizzup>
in any case I think this is in the rtcom query
ungeskriptet has quit [Read error: Connection reset by peer]
ungeskriptet has joined #maemo-leste
<dsc_>
that rant was actually meant for the Qt dev chat - wrong window. But regardless, its good you are all aware of my struggles :P
<_Gary>
Wizzup: moved el-v1.db to tmp and restarted, no change
diejuse has quit [Quit: Client closed]
<Wizzup>
_Gary: restarted means rebooted, right?
<_Gary>
yes
<Wizzup>
ok, I will have to try it on the pinephone then