xes has quit [Read error: Connection reset by peer]
xes has joined #maemo-leste
dev has left #maemo-leste [Disconnected: Replaced by new connection]
dev has joined #maemo-leste
Livio has quit [Ping timeout: 252 seconds]
Pali has joined #maemo-leste
Danct12 has quit [Remote host closed the connection]
Danct12 has joined #maemo-leste
dev has left #maemo-leste [Disconnected: Replaced by new connection]
dev has joined #maemo-leste
Pali has quit [Ping timeout: 268 seconds]
josuah has joined #maemo-leste
uvos has joined #maemo-leste
dev has left #maemo-leste [Disconnected: Replaced by new connection]
dev has joined #maemo-leste
xmn has quit [Ping timeout: 255 seconds]
xmn has joined #maemo-leste
Danct12 has quit [Remote host closed the connection]
Danct12 has joined #maemo-leste
pere has quit [Ping timeout: 240 seconds]
pere has joined #maemo-leste
Danct12 has quit [Quit: Leaving]
dev has left #maemo-leste [Disconnected: closed]
dev has joined #maemo-leste
<buZz>
lol, did 'a long voicecall' on leste, now my xorg seems locked, many programs open
<buZz>
i guess the proximity sensor doesnt work or sphone dailer doesnt use it
<buZz>
ah, does respond to long-power-button-holding
<sicelo>
:-)
<Wizzup>
buZz: yes, I don't think sphone deals with the proximity sensor yet
<buZz>
$soon
<buZz>
but, quality was topnotch
<buZz>
(after i put the 'voice' volume slider a bit higher, and enabled noise cancellation)
<Wizzup>
buZz: that should be enabled by default
<buZz>
it isnt on mine
<uvos>
mce should deal with the proximity sensor (if sphone puts it in the right mode)
<uvos>
its not working?
<Wizzup>
not for me afaik
<uvos>
(it cant work for me because its in lock-tklock)
<Wizzup>
I always lock the phone when calling
<uvos>
ok ill have to check whos at fault there
<uvos>
i assume every one else is running tklock
<Wizzup>
yes
Danct12 has joined #maemo-leste
SuperMarioSF has joined #maemo-leste
<SuperMarioSF>
hi
<SuperMarioSF>
I'm back
<Wizzup>
hi, I'mm not avail for debugging atm :)
<SuperMarioSF>
no problem
<SuperMarioSF>
my plan today is flashing another Droid 4
<SuperMarioSF>
however this time a little different
<SuperMarioSF>
this droid 4 have already installed LineageOS 14.1, kernel version 3.0.8, with kexecboot already installed.
<SuperMarioSF>
so I don't know what to do next. Should I just flash my SD card and just go with it?
<uvos>
it came with kexecboot installed?
<uvos>
yes you can just flash a sdcard
<SuperMarioSF>
so the file flashed on SD card already have necessary information to let an existing kexecboot installation just found the distro on the card?
<SuperMarioSF>
currently the kexecboot menu only show the android option and the settings menu.
<uvos>
yes
<SuperMarioSF>
OK
<SuperMarioSF>
Then I just flash a new card then.
<uvos>
kexecboot checks for /boot/boot.cfg on every partition
<uvos>
and then aggregates all boot entries
<SuperMarioSF>
what is the maximum capacity allowed on d4's controller? 32G?
<uvos>
there is none
<uvos>
or there is, but it huge
<uvos>
>2tb
<SuperMarioSF>
oh, then I can just toss a 128G card in it just fine.
<SuperMarioSF>
I got some really crappy card to test with. My extra durance card will arrive the day after.
<SuperMarioSF>
just test for fun at the moment
SuperMarioSF has quit [Quit: Client closed]
SuperMarioSF has joined #maemo-leste
<SuperMarioSF>
oh, crappy card indeed. only 5MB/s write speed.
<SuperMarioSF>
the kexecboot installed there is v0.6, seems working just fine.
<uvos>
the kexecboot version is not really related to our kexecboot relase
<uvos>
its just the version of the ui
<uvos>
please do upgrade it if its old, there was a fix that prevents some crashes in the os later (after boot)
<SuperMarioSF>
the first boot seems okay
<SuperMarioSF>
the only problem is d-pad control are sideways
mardy has quit [Read error: Connection reset by peer]
uvos__ has joined #maemo-leste
<uvos__>
wdym dpad? the arrow keys?
<uvos__>
also wdym sideways?
<uvos__>
in what app
<sicelo>
dpad nearly always means arrow keys, yes
<SuperMarioSF>
arrow keys in kexecboot v0.6
<SuperMarioSF>
the "up" is actually bind on left key
<SuperMarioSF>
that is not the case for kexecboot v0.8
<SuperMarioSF>
v0.8 works correctly
<SuperMarioSF>
but that isn't a big deal, since it boots kernel no problem
<SuperMarioSF>
I'm testing my other exactly the same crappy 128GB SD card, I doubt this card are fake since it was unbelievably cheaply made, and that was an addon for literally US$2 for some other thing that I bought.
Livio has joined #maemo-leste
mardy has joined #maemo-leste
Pali has joined #maemo-leste
SuperMarioSF has quit [Quit: Client closed]
<uvos__>
oh that
<uvos__>
that version of kexecboot is really old and must be replaced
<uvos__>
it will cause random failures in the booted kernel+
<uvos__>
its not fine
SuperMarioSF has joined #maemo-leste
<SuperMarioSF>
ok
<SuperMarioSF>
I guess I see some problems there.
<SuperMarioSF>
such as screen tearing
<SuperMarioSF>
rebooting and reflashing
<SuperMarioSF>
wait I must mixed something
<SuperMarioSF>
I just found out my working one running v0.6 of kexecboot
<SuperMarioSF>
there is no v0.8.4 after all...
<SuperMarioSF>
weird, where I see that version before...
<sicelo>
What's the driver for d4 modem? I want to unload and load it again
<sicelo>
Right now ofono isn't working, but that seems to be because modem itself is awol
<sicelo>
I do have ttyUSB[3,4] though .. not sure if that's the one, but i doubt
<uvos>
sicelo: there is not modem driver as sutch
<uvos>
its various
<uvos>
phy_mapphone_mdm6600 dose the usb if, snd_soc_motmdm the modem->cpu dai, gnss_motmdm gps
<uvos>
etc
<uvos>
also the "drivers" dont do a whole lot
<uvos>
phy_mapphone_mdm6600 just exposes the natvie interfaces of the modem to userspace
<uvos>
so im not sure reloading those would help if the modem itself is in a funny state
Twig has joined #maemo-leste
SuperMarioSF has quit [Quit: Client closed]
SuperMarioSF has joined #maemo-leste
<SuperMarioSF>
just fixed my stiff slide by applying some WD-40
<SuperMarioSF>
be warned not put too much, or WD-40 will leak into screen and that isn;t very easy for cleanup...
vagag has joined #maemo-leste
SuperMarioSF has quit [Quit: Client closed]
SuperMarioSF has joined #maemo-leste
SuperMarioSF has quit [Client Quit]
SuperMarioSF has joined #maemo-leste
<SuperMarioSF>
I wonder if OMAP3410 chipset can be supported by maemo-leste
<SuperMarioSF>
Motorola Charm and Motorola Flipout
<SuperMarioSF>
those device can be interesting
<sicelo>
i guess it's time for a reboot then. sigh
<uvos__>
SuperMarioSF: Wizzup was interested in makeing sholes based devices work
<uvos__>
SuperMarioSF: but that would come in the form of xt610 or maybe a855 at first
<uvos__>
also imo its a waste of time
<sicelo>
SuperMarioSF: looks like 3410 isn't much different from N900's 3430, so should be doable
<sicelo>
hah! no SGX at all in it
<SuperMarioSF>
there is no info about dsp in 3410 tho...
<sicelo>
well ... dsp is not used on N900 either
<uvos__>
yeah nvm looks like those are not sholes, there even older platform wise
<uvos__>
? the dsp is used for video decoding no?
<uvos__>
imo its even more of a waste of time to do something <sholes
<sicelo>
SuperMarioSF: if you have bootloader issue handled, i'm sure those devices can be well supported in pmOS at least
<sicelo>
damn ... those devices have very interesting design. me likey
SuperMarioSF has quit [Quit: Ping timeout (120 seconds)]
SuperMarioSF has joined #maemo-leste
<sicelo>
SuperMarioSF: do you have these devices, or just asking out of interest?
uvos__ has quit [Ping timeout: 268 seconds]
SuperMarioSF has quit [Ping timeout: 252 seconds]
SuperMarioSF has joined #maemo-leste
<SuperMarioSF>
just out of interest. however if needed, I can just buy one very cheap.
<SuperMarioSF>
well not that cheap.
<SuperMarioSF>
average 200~300CNY
<SuperMarioSF>
no one seems old stock, all used. some even doesn't have battery.
<SuperMarioSF>
they were selling as "Game Console Emulation Phone" because the QWERTY keyboard.
<sicelo>
I guess buying one would indeed be a waste as uvos says. But working on one you already own is a different matter
<SuperMarioSF>
I don't have one, but I would like to have something like that in my collection.
<SuperMarioSF>
so far Droid 4 served me well.
<SuperMarioSF>
it is very likely to became a daily driver for me.
<Danct12>
sorry for a offtopic question, but i'm currently adapting wl1251-cal to postmarketOS and for some reason fallback mechanism fails to work on boot
<sicelo>
those were Wizzup's and my experiences back then. i doubt anyone's looked into it much since then
<SuperMarioSF>
so I have a question then...
<SuperMarioSF>
battery gauge says need calibration
<SuperMarioSF>
how can I do that manually?
<SuperMarioSF>
I didn't see anything I can just run in package droid4-battery-calibration
<sicelo>
charge it to full, allow it to drain to empty ... you can let this happen naturally. at some point towards completely empty, it will auto-calibrate
<sicelo>
ymmv
<SuperMarioSF>
ok
<SuperMarioSF>
what if power just suddently down while battery percentage isn't nearly as low? Is that will still works?
<sicelo>
i think this is also in wiki :-)
<Wizzup>
not sure, our doc isn't that great, at least structure wise
<sicelo>
SuperMarioSF: hence the 'ymmv' ... if you're luckly, it will still be considered. otherwise, you need to repeat the steps
<Wizzup>
sicelo: Danct12: can look in an hr or two
<SuperMarioSF>
just looked up on wiki, no such thing were mentioned anywhere...
<SuperMarioSF>
but I remember I may read something about battery calibration script in news, it doesn't talked about how it works either.
<sicelo>
ah. it's a bit hacky, but works some. the problem is that under linux/Leste, cpcap (currently?) doesn't store the calibration itself, nor does the battery. the script attempts to do this using a file
<SuperMarioSF>
ok
<SuperMarioSF>
so I will try that after I replaced my battery.
akossh has joined #maemo-leste
<buZz>
you dont need a script to calibrate the battery
<buZz>
just : 1) deplete battery without shutting down leste, so you get the 'recharge battery' popup with 'pooodoonk' sound , 2) charge it -once- fully to 100% , 3) repeat 1) , then redo 2) , it will update the measurement
<buZz>
every time you do this , it will update the known/measured mAh from the battery you have
<buZz>
'charge fully to 100%' is till the green led goes -off- and message 'disconnect charger' appears , plus battery says 'fully charged' in statusmenu etc
<sicelo>
it's just that you don't need to manually use it :-)
<sicelo>
otherwise your precious calibration data vanishes on a reboot
<buZz>
ah yeah, indeed
<sicelo>
mmm, i actually have a PR against that package. i wonder why it wasn't merged :-/
<Wizzup>
maybe it was missed
Twig has quit [Ping timeout: 252 seconds]
vagag has left #maemo-leste [Error from remote client]
SuperMarioSF has quit [Quit: Client closed]
dev has left #maemo-leste [Disconnected: Replaced by new connection]
dev has joined #maemo-leste
mardy has quit [Quit: WeeChat 2.8]
akossh has quit [Remote host closed the connection]
Livio has quit [Ping timeout: 268 seconds]
<uvos>
about cpcap/calibration data
<uvos>
theres no where to store it hw wise, except on the battery eeprom but motorola dident do that, and we dont know what the values on the eeprom mean so we cant just change them
<uvos>
motorola dident use the hw state of charge capabilities of cpcap at all
<uvos>
the reason why i dident merge that pr is, even though that is my pacakge
<uvos>
i dont have the rights to the git repo
<uvos>
and i gues it was forgoten that i requested that
<uvos>
Wizzup: ^^^
<uvos>
easiest way to ensure battery callibration is for me this btw: let the device drain untill empy, boot the device by pluging in usb and wait for the battery display of charge mode, quickly unplug and replug the usb lead, press power to boot to normal mode, charge fully, shutdown (to ensure its saved because d4 is still a bit unstable and a sucessfull normal shutdown is required)
ikmaak2 has quit [Ping timeout: 240 seconds]
ikmaak has joined #maemo-leste
ikmaak has quit [Read error: Connection reset by peer]