<uvos>
the heuristic here being if the desktop file is in hildon subdir or not
<uvos>
its not that ideal tho since it affects only applications launched via h-d, not xterm or so
<Wizzup>
well what I mean is here the qt platform plugin could know automatically if it is maemo without the app calling setProperty("X-Maemo-Style", "maemo")
<uvos>
also idk if autodetecting the scale factor in particular is sane
<Wizzup>
yeah, not sure if it is
<uvos>
its not
<Wizzup>
btw that PR has 'X-Maemo-Hilon' everywhere
<Wizzup>
not 'X-Maemo-Hildon'
<uvos>
Wizzup: this pr is abandoned
<uvos>
since freemangordon dident like it at all
<uvos>
so it wont be merged ever anyhow
<Wizzup>
ok
<Wizzup>
maybe close it then as such
<uvos>
well i like mergeing it privately, but yeah i can keep it in a branch instead
<uvos>
anyhow so with some applications i use fusion and a scale factor, with others i use maemo style (which is bigger allready) and no scale factor and with some i use maemo style and a scale factor (mostly qml)
<uvos>
so scale heurisic istent going to work imo
<Wizzup>
right
<Wizzup>
your qml apps automatically get the maemo style?
akossh has joined #maemo-leste
<uvos>
no ofc not (besides dialogs and sutch) thats not how qml works
<uvos>
tmlind: btw i disagree to calling the phone common dts "droid"
<uvos>
1. the xyboard was sold as the droid xyboard when sold via verizon contract
<uvos>
2. the name "droid" was owned by lucas arts and licenced to verizon only, and they used this name as a prefix or as the name of all thair devices during this time period, not just motorola devices
<uvos>
3. because the the droid name was licenced to verizon not motorola all the phones where sold under other names outside the us (ie droid 1/2/3/4 -> milestone 1/2/3/4, droid razr -> razr etc)
<Wizzup>
uvos: dpkg -L linux-image-omap has all the DTBs it seems
<Wizzup>
so as long as you add it to kernel makefile it should be fine
<tmlind>
uvos: well do you have some better name in mind? i used motorola-mapphone-phone.dtsi, but has phone twice..
<buZz>
but would be nicer to use the fs program without having to do ctrlshiftN all the time :P (or volume buttons)
<buZz>
can i force it alwayson for a program?
<Wizzup>
yes, this is an atom the program can set afaik
<uvos>
there is a hildon hint
<Wizzup>
I don't know if it fully overrides it
<uvos>
but this is silly
<uvos>
since h-d can just do what every other wm dose
<uvos>
and suspend whenever there is only one window
<Wizzup>
looks like my mz617 is android 4.1.2
<buZz>
well, chromium improves greatly in speed from having it on
<uvos>
working on mz617 is painfull, no sdcard no allow-mbmloader...
<uvos>
no bpsw, flashing kexecboot to cache makes android buggy
<buZz>
even 'windowed' you can notice the speed difference a lot
<uvos>
yes compoiting is extreamly hevy
<buZz>
no, -without- compositing it is slower
Juest has joined #maemo-leste
<uvos>
thats wierd
<buZz>
try it
<buZz>
with it on, i can even use youtube, without its too slow
<uvos>
at least scrolling on bbc news
<uvos>
suspended is mutch faster
<buZz>
try in hildon
<uvos>
yes in hildon
<Wizzup>
uvos: well it sounds like tmlind had it working
<buZz>
not what i'm seeing, lol
<uvos>
Wizzup: might be android 4.1 vs 4.0.4
<uvos>
we both have 4.0.4
<uvos>
tmlind: ^^ ?
<Wizzup>
uvos: I mean on mz617
<uvos>
what now
<uvos>
my mz617 works fine
<uvos>
booting android after kexecboot
<uvos>
but you break androids chache
<uvos>
that dosent stop it form booting
<uvos>
but there are issue
<uvos>
s
<Wizzup>
yeah, so my remark about tmlind had it worked was about mz617, and your comment wrt kernel versions was about razr :)
<uvos>
right
<Wizzup>
kind of a shame that the mz617 doesn't have a microsd card yeah ;)
<Wizzup>
slot*
<uvos>
and the bootloader...
<uvos>
it has a microsdcard slot btw
<Wizzup>
hm
<uvos>
motorola dident populate it on us variants
<Wizzup>
I was looking at mine and it looks like there's space for it
<uvos>
for some reason
<uvos>
but its there
<uvos>
behind a plastic cover
<uvos>
(the footprint, its not populated)
<Wizzup>
ah, so if you cut the plastic open it is there? ok
<Wizzup>
ok, so without a holder
<uvos>
yes
<Wizzup>
well, that's not too hard to fix :p
<buZz>
hmhm yeah, after volumebar fades out, it switches comp back off, slow again, ONLY on fullscreen, not on windowed
<Wizzup>
buZz: so 'comp off' and 'slow again' doesn't make sense to me
<Wizzup>
you mean 'comp on'
<buZz>
Wizzup: no
<Wizzup>
unless I'm going nuts
<uvos>
he is reporting some bug
<Wizzup>
how can compositing being off make things slow?
<uvos>
i cant repo it
<Wizzup>
aha
<tmlind>
uvos: yeah cache can be flashed.. could not find other partition
<uvos>
omapddx could misbehave
<buZz>
comp -off- on -fullscreen- chromium windows makes them slower
<uvos>
with comp on h-d renders the frame
<uvos>
off omapddx dose
<tmlind>
Wizzup: care to flash cdma_spyder_9.8.2O-72_VZW-16_1ff.xml.zip. on your xt912 and i'll provide an experimental kexecboot image to try?
<uvos>
there might be something wrong in omapddx
<buZz>
uvos: it does render, but a lot slower
<tmlind>
we need to figure out how to extract the initramfs address dynamically..
<buZz>
might be the 'reboot device, your gpu is in weird state'
<buZz>
i'll try
<Wizzup>
tmlind: I will need to find that image first, but then I'm happy to try. I also have two here, one with kernel 4.1.2 (or so), if that's what you'd like me to try?
<Wizzup>
uvos: wait, is your razr 4.0.4 or 4.1.2 ?
<uvos>
4.0.4
<Wizzup>
ok
<uvos>
my 4.1.2 razr is also 404
<Wizzup>
I don't understand that :)
<Wizzup>
404 as in http?
<uvos>
yes i dont have one
<uvos>
fixed @pr
<Wizzup>
I thought you didn't do jokes
<Wizzup>
;)
<uvos>
who says what is joke and what is not?
<Wizzup>
the joke police?
<Wizzup>
uvos: btw the leste-config change was for Section: droid4, I assumed that was intended
<uvos>
yeah
<tmlind>
Wizzup: here are the xt912 test images to try after you've updated the firmware to cdma_spyder_9.8.2O-72_VZW-16_1ff.xml.zip http://muru.com/linux/d4/test/
<uvos>
Wizzup: btw images
<uvos>
we should just disrobute boot and root seperatly
<uvos>
hmm nvm
<uvos>
that dosent help because of leste-config
<uvos>
what is cdma_spyder_9.8.2O-72_VZW-16_1ff.xml.zip?
<uvos>
android version wise
<uvos>
i dont know if updateing to 4.1 and blowing the fuse is a good idea
<Wizzup>
uvos: I was planning to use my 4.1.x one
<Wizzup>
if that makes sense
<uvos>
then it probubly wont work if its not a 4.1 image
<uvos>
at least thats how it works on bionic
<tmlind>
anybody have a good shell trick in mind to extract the initramfs address with busybox sh? multiple matches with grep -oban $'\x1f\x8b' boot.img..
<buZz>
alright, took 4 powercycles, but now chromium fullscreen is just as fast with compositing enabled as disabled
<Wizzup>
tmlind: I can try to help, if that's the grep command to start out with
<uvos>
hmm
<uvos>
@buZz
<buZz>
guess its the gpu bug freemangordon spoke about before
<uvos>
probubly
<uvos>
vsync behavior is different in these modes
<uvos>
must be some timeing bug with cm pannel
<buZz>
-some- boots he couldnt get yt playing fast, but 'normally' it works
<buZz>
uvos: could you have the sphone txt displays be selectable? so i could copypaste numbers from it to contacts
<buZz>
specifically the sms inbox
<uvos>
sure but needs some thought how to do exactly
<buZz>
maybe just a longhold->copynumbertobuffer ?
<uvos>
dunno
<uvos>
needs to work well on desktop and on leste
<uvos>
needs some thought as i say
<buZz>
either way its now 'write number on paper' and then switch to other
<buZz>
program to enter it
<buZz>
lol
<uvos>
sure it needs some kind of method
<uvos>
maybe you can copy from abook (for now)?
<buZz>
nope
<buZz>
you cant get details for contacts that dont exist, try it
<uvos>
ok
<buZz>
adding a 'import this unknown contact' in abook would be cool too
<buZz>
ooo, i guess i could just dump the db in xterm and copy there
<uvos>
or allways run sphone in verbose mode and copy it from its logs xD
<Wizzup>
tmlind: busybox xxd -p -c 10000000 boot.img this can make it one simple line of hex, and with normal grep you can then find the offset with --byte-offset
<Wizzup>
but busybox grep doesn't have --byte-offset
<uvos>
Wizzup: btw regarding not building almost identical images.
<uvos>
at least we are not behind here, even los with a huge amount of devcies in support do this
<Wizzup>
yeah, it's just that it's slow I guess, that's what bothers me
<Wizzup>
in the next two months my living place should stabilise and I'd have more room to improve it
<Wizzup>
s/place/situation/
<Wizzup>
uvos: I can try to build a razr image?
<Wizzup>
I guess we might need a meta update for it
<uvos>
yes
<uvos>
theres more stuff
<Wizzup>
apart from hildon-meta ?
<uvos>
no probubly not
<uvos>
but i was going to try and flash d4 image
<uvos>
update to expiramental on d4
<Wizzup>
yeah that's easier/better
<uvos>
and then change boot.conf by hand
<uvos>
and shove the sd into a razr
<Wizzup>
cp: cannot stat '/usr/lib/linux-image-omap/omap4-razr-xt910.dts': No such file or directory
<Wizzup>
maybe I'm not n experimental
<buZz>
maybe we just need a faster CI server? :P
<uvos>
buZz is paying
<buZz>
hehe
<Wizzup>
I don't think buzz has any idea how fast it already is
<buZz>
what do we have? maybe i can find some hw for free
<uvos>
thats why he is paying
<Wizzup>
it's just the image building process itself that involves a lot of network fetching and otherwise i/o stuff on loopback mounted cr*p
<tmlind>
dd if=${boot_img} skip=${initramfs_offset} bs=1 count=4 | hd
<Wizzup>
sweet
<Wizzup>
did you still need me to try this .xml.zip file, and shall I try it on my already 4.1.2 razr then?
<tmlind>
Wizzup: sorry can't follow what you mean, which firmware do you have now?
<Wizzup>
tmlind: so I had a razr with some 4.0.4 on it, that I didn't clean-flash, and I put kexecboot on that one. I also have a 4.1.2 razr that I haven't put kexecboot on it yet, then you asked me to try it (kexecboot) with cdma_spyder_9.8.2O-72_VZW-16_1ff - which is 4.1.2 iiuc
<Wizzup>
uvos said maybe it's not a good idea to upgrade my 4.0.x to 4.1.x so I said I can flash it to the razr that is already on 4.1.2
<Wizzup>
I'm just checking if you still wanted me to flash cdma_spyder_9.8.2O-72_VZW-16_1ff to my 4.1.2 and see if kexecboot works with that
<tmlind>
Wizzup: ok if you did not yet update, please just wait a bit then :)
<Wizzup>
ok :)
<uvos>
Wizzup: booting a new d4 image
<uvos>
it stalled for a really really long time generating ssh keys
<uvos>
probubly rand starvation
alex1216 has quit [Quit: WeeChat 2.3]
<tmlind>
somehow similar changes in preinit.sh are not working yet.. need to debug with a serial console at some point, have to give up for now
<uvos>
aand like an idiot i pushed the sdcard into xt910's simcard slot
<uvos>
and now having a hard time getting it out
<norayr>
uh
<norayr>
sicelo, i got an n900 from someone who knows me and doesn't want to use it anymore.
<norayr>
but no leste on it yet.
<norayr>
i checked live wallpaper and apparently the board there doesn't have a message under fremantle as well.
<norayr>
so i need ho figure out where the message should come from, if there should be any.
<norayr>
maybe some http connection became https?
<norayr>
or maybe the site doesn't exist anymore.
<norayr>
anyone remembers live wallpaper's modern theme behaviour ten years ago?
<uvos>
my xt910 is in hildon!
<uvos>
tmlind: theres something wrong with the pannel timeing
<uvos>
tmlind: it rolles like a tv out of hsync
<uvos>
sensors dont work yet
<uvos>
interesting
<uvos>
on xt910 the buttons on the bottom are _not_ part of the main touch screen
pere has quit [Ping timeout: 256 seconds]
<sicelo>
norayr: i never used live wallpaper
<uvos>
none of the leds work
<uvos>
besides notification
<tmlind>
uvos: cool that you got it going :)
<tmlind>
later
<Wizzup>
uvos: sweet
<uvos>
Wizzup: im doing inital wiki page
<uvos>
im noticing how out of date the d4 page is....
<uvos>
can you include stuff on media wiki
<uvos>
ie if i write a section on bluetooth
<uvos>
can we just include that on the xt875,xt894 and xt91x pages?
<sicelo>
using templates is one of the best/easiest ways to achieve that
<uvos>
sicelo: no the mainline kernel resets these resigers as part of its inialization code
<uvos>
you have to patch the driver
<uvos>
cpcap is on spi
<buZz>
afaik the mainline kernel -does- have support to blink that led, at least in white ... i think maybe other colors too?
<buZz>
even has a 'charging' triggermode
<buZz>
not sure if it would be flashing though, hmm
<sicelo>
when connected to a charger, the led becomes green and cannot be controlled. you can write any value to /brightness, with no effect
<sicelo>
but yes, at other times, you can do what you want
<buZz>
right
<buZz>
maybe the keyboard capslock light can be used for your purpose? :D
<sicelo>
no. because that requires keyboard to be slid out first before it can be useful as a notification light
<sicelo>
anyway, i just wanted to know if there was no way to retain control of that LED while charging
<sicelo>
fwiw, N900's charger also does the same thing to the LED, except in its case, it's not hard to disable that function and retain control of LED
<uvos>
its not hard with cpcap either
<uvos>
just 1 bit in a register
<uvos>
the problem is more that there is not really a standart userspace interface you could use
<uvos>
also personally i dont care since i like the hw control
uvos has quit [Quit: Konversation terminated!]
<buZz>
sicelo: ooo, the backlight of the 4 hw touchbuttons? :D
<buZz>
hahaha
<buZz>
hahahahahahaha, as root ; echo "battery-charging-blink-full-solid" > /sys/class/leds/button-backlight/trigger
<buZz>
not sure if it works when screen is off
<buZz>
i guess not :/
<buZz>
hmm oh, someone is turning off the trigger :D