| yifei1 | Wizzup: neat, I think it's better we avoid repeating the same work | 01:24 |
|---|---|---|
| Wizzup | I can share more details sunday eve or monday | 01:27 |
| tmlind | sicelo: thanks :) | 11:44 |
| Wizzup | yifei1: I'll see if I can start my pinephonepro tomorrow | 14:08 |
| Wizzup | I should have the tar somewhere | 14:08 |
| Wizzup | iirc the remaining problem was that the hdmi port was being seen as connected and somehow used as output/display | 14:08 |
| _Gary | lost ability to do SMS and reply to SMS | 23:14 |
| _Gary | both sphone new SMS and SMS history crash when trying to open | 23:15 |
| _Gary | i can bring up the conversations SMS and see the message but unable to reply cannot type into the message field | 23:16 |
| _Gary | keyboard does not activate, on a pinephone | 23:17 |
| _Gary | deb leste chimaera-devel main contrib non-free lima pinephone | 23:17 |
| _Gary | recently did a update and upgrade | 23:18 |
| Wizzup | I'll see if I can figure out tomorrow why the rtcom db reset would be necessary for conversations/ring to work | 23:27 |
| 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 | 23:27 |
| 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 | 23:28 |
| Wizzup | s/messes/messed/ | 23:28 |
| _Gary | okay many thanks for looking into this | 23:33 |
| Wizzup | for now I think you can 'fix' it by moving the rtcom-el-v1.db elsewhere | 23:37 |
| Wizzup | and then restarting | 23:37 |
| _Gary | I'll give that a try, thanks | 23:38 |
| dsc_ | for Qt7 they ought to nuke how tables work imo | 23:48 |
| dsc_ | needs a much simpler API | 23:48 |
| 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 | 23:48 |
| 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 | 23:50 |
| dsc_ | perhaps the author tried his best to make it as confusing as possible. only logical conclusion I have | 23:51 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!