belcher_ has joined #maemo-leste
belcher has quit [Ping timeout: 240 seconds]
cockroach has quit [Quit: leaving]
sunshavi has quit [Remote host closed the connection]
ceene has joined #maemo-leste
<AaronBurr> it's so funny how the Maemo low battery sound sounds so sad :)
xmn has joined #maemo-leste
joerg is now known as Guest5891
joerg has joined #maemo-leste
Guest5891 has quit [Ping timeout: 245 seconds]
mardy has joined #maemo-leste
<Danct12> not until you hear the recharge battery sound
<AaronBurr> that's more a cry of help than a sad sound though
<AaronBurr> I haven't found cause of the gl4es fullscreen messup on droid4. I'm surprised others haven't report it. It appears as diagonal lines, and a repeat will eventually require a reboot.
belcher_ is now known as belcher
Pali has joined #maemo-leste
belcher has quit [Remote host closed the connection]
belcher has joined #maemo-leste
belcher has quit [Read error: Connection reset by peer]
belcher has joined #maemo-leste
Pali has quit [Ping timeout: 276 seconds]
alex1216 has joined #maemo-leste
uvos has joined #maemo-leste
<sixwheeledbeast> I just recalled the old nokia I'm flat switching off noise... welp
<Wizzup> can't parse
<uvos> so i managed to contact one of the guys who used to run a german forum on motorola devices
<uvos> and he thinks he can grab the mz61X files from a old backup of his
<sixwheeledbeast> bad grammr probably.
<uvos> so thats great
<Wizzup> uvos: yay!!
<uvos> btw Wizzup i also contacted the sphone author and offered him a droid 4 if he wants to help us any with his old application.
<Wizzup> uvos: if he has more motorola files to share, maybe we can host a backup
<uvos> i assume thats fine
<Wizzup> uvos: yeah of course that's fine
<Wizzup> uvos: feel free to do that 10 more times to other folks :p
<uvos> ok :)
<Wizzup> I'm also bringing freemangordon a mz617
<uvos> nice\
<uvos> hmm
<uvos> x needlessly refreshes the display every second in the present ext.
<Wizzup> not sure if that is true for us atm
<uvos> no we dont use present afaik
<uvos> but it would be if we switch to ddk1.17
<Wizzup> right
inky has quit [Ping timeout: 268 seconds]
inky has joined #maemo-leste
inky has quit [Ping timeout: 258 seconds]
inky has joined #maemo-leste
xmn has quit [Ping timeout: 256 seconds]
uvos has quit [Ping timeout: 245 seconds]
uvos has joined #maemo-leste
inky has quit [Ping timeout: 250 seconds]
inky has joined #maemo-leste
inky has quit [Ping timeout: 258 seconds]
inky has joined #maemo-leste
Pali has joined #maemo-leste
cockroach has joined #maemo-leste
uvos has quit [Ping timeout: 252 seconds]
uvos has joined #maemo-leste
<uvos> parazyd: any idea how devuan decides what debian pacakges to build for thier repos?
<tmlind> Wizzup: yeah sorry i think i deleted my dtc branch after dtc got integrated to the kernel :( so far no luck finding that patch, and it was not very usable anyways like uvos pointed out
<parazyd> uvos: If one wants to maintain a pkg, it can be built
<parazyd> uvos: Otherwise, only if there is a (semi) hard dep on systemd
<tmlind> Wizzup, uvos: anyways, i uploaded stock mz619 dts in case that's what you're looking for http://muru.com/linux/d4/mz617-stock.dts
<uvos> tmlind: we where mostly looking for the dts for xt862
<uvos> tmlind: but thanks anyways for the mz619 dts
<tmlind> uvos: ok, don't have that one
<tmlind> the dtc patch i had just did endian swapping in some header
<uvos> do you also have mz609?
<uvos> dts
<uvos> not that i expect it to be different, at all maybe
<tmlind> don't have that either
<uvos> ok
<tmlind> probably just different lcd params
<uvos> tmlind: dmesg suggests not even that
<tmlind> ok
<uvos> how about xt894?
<tmlind> i have that one, will upload
<uvos> ill upload whatever i get/have there
<tmlind> ok i uploaded the ones i have to http://muru.com/linux/d4/stock-dts/
<uvos> great
<uvos> ill mirror those
<tmlind> ok great
<uvos> i rationalized http://uvos.xyz/maserati a bit
<uvos> tmlind: btw mz61x with unlocked bootloaders existed
<uvos> tmlind: there are users on xda with screenshots of unlocked mdm
<uvos> it seams like the developer program that existed for xt910 existed for mz61x too
<tmlind> oh interesting
<uvos> maybe Wizzup should check all of his
<uvos> but it looks like this involved only the eu mz615
<tmlind> ok
<tmlind> maybe all mz615 are unlocked?
<uvos> no
<tmlind> hmm no
<tmlind> i have one somewhere and it was locked..
<uvos> seams like just randoms ones
<uvos> btw do you know how mz617 active stylus worked? im kinda puzzeld reading the touchscreen datasheet
<uvos> and i dont have one
<tmlind> no idea, is that some separate product for the stylus?
<uvos> tmlind: the stylus was packaged with the device
<uvos> in us only
<uvos> on verizon only (not the wifi model)
<uvos> ofc when we buy the devices used we never get the stylus
<uvos> afaik none of us have one
<tmlind> ok, i bought all my devices used from ebay, never saw any stylus or at least did not notice one in the packaging..
<uvos> ok
<tmlind> maybe we all got them but threw them away with packaging :)
<uvos> he
<uvos> anyhow its active, as in takes battiers and the stock fw has a special mode for it
<tmlind> weird
<tmlind> seems like you could get one for 4.21 https://www.ebay.com/p/2255875956
<uvos> that is unlimited times more than i paied for the device but yeah
<uvos> i might go that route
<uvos> :P
<tmlind> sell some custom scsi cables to finance the purchase :)
* tmlind zzz
Daanct12 has joined #maemo-leste
Danct12 has quit [Ping timeout: 240 seconds]
<uvos> tmlind: so in looking into why the charging on mainline might be so wierd i was looking at the cpap registers again
<uvos> tmlind: and noticed some random things
<uvos> tmlind: both android and mainline in charging and mostly the same state:
<uvos> tmlind: why are we setting CPCAP_REG_VHVIOC to a wildy different voltage
<uvos> tmlind: that looks like a bug
<uvos> tmlind: whats up with the registers over 0x7c98, the bootloader/reset state sets these to various values and we dont do anything with these
<uvos> tmlind: while android clears all of these to 0
<uvos> tmlind: both mainline kernel and moto kernel profess to be setting vhvio to the same value 2775000 but they end up with differing values for the acctual register
<uvos> so yeah looks like there is a (dangerous) bug here
jr-logbot has quit [Remote host closed the connection]
jr-logbot has joined #maemo-leste
alex1216 has quit [Quit: WeeChat 2.3]
n900 has quit [Ping timeout: 245 seconds]
n900 has joined #maemo-leste
Pali has quit [Ping timeout: 240 seconds]
uvos has quit [Ping timeout: 272 seconds]