<Wizzup>
I might recommend hiding some of the UI elements though, like the tabs and other things, but that's for later :)
<Wizzup>
tested on droid 4
xmn has quit [Ping timeout: 256 seconds]
elastic_dog has quit [Ping timeout: 265 seconds]
k1r1t0 has quit [Ping timeout: 260 seconds]
elastic_dog has joined #maemo-leste
__20h__ has quit [Server closed connection]
__20h__ has joined #maemo-leste
joerg has quit [Ping timeout: 258 seconds]
joerg has joined #maemo-leste
fab_ has joined #maemo-leste
ceene has joined #maemo-leste
fab_ has quit [Quit: fab_]
lightbringer has quit [Ping timeout: 265 seconds]
akossh has joined #maemo-leste
Daanct12 has quit [Ping timeout: 240 seconds]
fab_ has joined #maemo-leste
Danct12 has joined #maemo-leste
xmn has joined #maemo-leste
<norayr>
freemangordon: i still think i just didn't install something which would cause my d4 to vibrate. i am sure nothing is broken, because it was working before my sdcard failed.
<norayr>
i think i miss some package.
lightbringer has joined #maemo-leste
lightbringer has joined #maemo-leste
lightbringer has quit [Changing host]
sicelo has quit [Server closed connection]
sicelo has joined #maemo-leste
lightbringer has quit [Ping timeout: 265 seconds]
lightbringer has joined #maemo-leste
lightbringer has quit [Changing host]
lightbringer has joined #maemo-leste
udder has quit [Quit: die in fire]
udder has joined #maemo-leste
xmn has quit [Ping timeout: 258 seconds]
xmn_ has joined #maemo-leste
xmn_ has quit [Client Quit]
xmn has joined #maemo-leste
uvos has joined #maemo-leste
<uvos>
norayr: really only the kernel, mce and hh are involved in vibration
<uvos>
none of those can not be installed without more serious side effects
<uvos>
besides something being missing in the image is a bug in and of itself
<uvos>
vibration only dosent work via xdg desktop notifications right?
<uvos>
ie sphone can vibrate fine
norayr has left #maemo-leste [Disconnected: timeout during writing]
fab_ has quit [Quit: fab_]
fab_ has joined #maemo-leste
norayr has joined #maemo-leste
ceene has quit [Ping timeout: 240 seconds]
RedW has quit [Quit: huh upgrades]
RedW has joined #maemo-leste
fab_ has quit [Quit: fab_]
le0nklcpp has joined #maemo-leste
<le0nklcpp>
Wizzup_: thanks, tabbar is the only thing that can't be turned off in settings :)
<Wizzup>
le0nklcpp: right
<Wizzup>
ah, I see
<Wizzup>
I think we'd ultimately just want a window instead of a tab, not sure
<maxwelld>
yes email vibrates.
<uvos>
for ff i hide the tab bar using some custom css, i think falkon uses qwidgets not browser rendered html for the ui elemetns, right?
<le0nklcpp>
right, hiding tabs will require some code
fab_ has joined #maemo-leste
elastic_dog has quit [Ping timeout: 240 seconds]
le0nklcpp has quit [Quit: Leaving]
elastic_dog has joined #maemo-leste
attah has quit [Server closed connection]
attah has joined #maemo-leste
le0nklcpp has joined #maemo-leste
norayr has left #maemo-leste [Error from remote client]
<tmlind>
heh soo.. looks like i was trying to debug i2c device with wrong id.. the tc358765 is on i2c1 at 0xf and not at 0x50.. 0x50 is some eeprom
<tmlind>
i can now read and write tc358765 regs with i2c-tools, the problem of mipi commands not making is still exists
<tmlind>
control over dsi won't do anything, need to still debug that at lease
<tmlind>
at least
* Wizzup
gets excited thinking about mapphone tablets every time
<tmlind>
heh yeah i too have been waiting for years now :)
<tmlind>
for reference, here are the i2c commands to read and write tc358765 regs
<tmlind>
at least gpio_45 must be high to read and write to tc358765 over i2c, probably gpio_101 too
<tmlind>
read tc358765 id register
<tmlind>
i2ctransfer -y -f 0 w2@0x0f 0x05 0x80 r4
<tmlind>
write to tc358765 sysrst register without resetting i2c
<tmlind>
eeprom at 0x50, gpio_40 must be high all the time for eeprom write protect to avoid trashing it, otherwise no lcd for android either
<tmlind>
also gpio_46 must be high to read eeprom
<tmlind>
no idea what's in the eeprom and why the lcd would depend on it
norayr has joined #maemo-leste
asriel has quit [Quit: Don't drink the water. They put something in it to make you forget.]
<Wizzup>
maybe some timing data
<Wizzup>
(for the display)
<tmlind>
yeah could be the clock is wrong
<tmlind>
anyways, i can now properly verify if and when the mipi dsi write to the registers does something
<Wizzup>
great :)
norayr has left #maemo-leste [Error from remote client]
maxwelld has left #maemo-leste [Error from remote client]
arno11 has joined #maemo-leste
<arno11>
Wizzup: sicelo: hi guys, few lines need to be modified in ucm to avoid noise in headphone. I'll send you an email soon.
<Wizzup>
great, ty
<sicelo>
arno11: thank you :-)
<arno11>
no probs :)
<sicelo>
Wizzup, tmlind, freemangordon, any suggestions for where one could start chasing kernel issue leading to the output at https://paste.debian.net/1283753/ ?
fab_ has quit [Quit: fab_]
<Wizzup>
sicelo: this is not an answer, but any idea what you were doing while this occurred?
<Wizzup>
and which kernel / device?
<sicelo>
it happens intermittently, at boot. I'm currently on 6.3.5, Nokia N900
<Wizzup>
is this with off mode on?
<Wizzup>
as in, is this with patches?
<sicelo>
vanilla, unmodified kernel
<Wizzup>
ok
<Wizzup>
so I don't know how to fix it, but I've ran into it plenty too
<Wizzup>
this is traced back all the way to when they enabled off mode by default
<Wizzup>
happens randomly on boot, and then it doesn't anymore since it never hits off (at least in leste), so the instability is gone there
<sicelo>
mmm, in my case, it completely hangs the kernel. can't do anything further