reallll has joined #maemo-leste
belcher_ has quit [Ping timeout: 265 seconds]
cockroach has quit [Quit: leaving]
joerg is now known as Guest2436
Guest2436 has quit [Killed (copper.libera.chat (Nickname regained by services))]
joerg has joined #maemo-leste
Twig has joined #maemo-leste
reallll is now known as belcher
xmn has quit [Ping timeout: 268 seconds]
Pali has joined #maemo-leste
inky has quit [Quit: Leaving.]
inky has joined #maemo-leste
inky_ has quit [Ping timeout: 265 seconds]
uvos has joined #maemo-leste
<uvos> inky: we really just need to figure out how to swtich input language in him on the fly
<uvos> inky: the problem is that him gets a string of random utf8 chars
<uvos> inky: and then must decide what xkeymap to switch to
<uvos> inky: not sure how to approch that
<uvos> inky: as a temporary hack you can take a d4 keymap and add any chars you want to write with the vkb by assingning them any free keycode between 30-250
<uvos> then you can type 2 or how ever manny languages you can fit into that space
<uvos> Wizzup: yes that would make ucm fail
<stano_> on d4, 5.11, getting a lot of usb disconnects/reconnects, about once a minute
<stano_> with 'exception stack' stuff in /var/log/messages
<stano_> maybe something is doing bad usb things
<stano_> maybe usb autosuspend is culprit
<stano_> now i've got flashing green light and constant reconnects :/
<stano_> looks like the powered i-tec usb hub is giving me a stable connection though
pere has quit [Ping timeout: 252 seconds]
<Wizzup> uvos: mh
<stano_> having a few different powered usb hubs seems to be a good thing. i have two here that droid4 is happy on, one that it is not.
<Wizzup> I don't use a hub on my d4 really, I rarely do that on my phone
<stano_> in my case right now, droid4 is not acting as host
<uvos> cpcap is picky about otg devices
<uvos> no idea why
<uvos> but its the same on android
<stano_> that hub you posted a pic of works nicely as otg hub uvos
<stano_> others, notsomuch
<uvos> i think its just a stickler for spec, it will immidatly cut devices off that dont negotiate power correctly
<uvos> for instance
<stano_> i just started losing wifi again today, on the AP next to the desk, so i'm back to usb networking
<Wizzup> 11:35 < uvos> inky: we really just need to figure out how to swtich input language in him on the fly
<stano_> better this way
<Wizzup> this is possible with a key combo
<Wizzup> sym+spcae ?
<uvos> Wizzup: no
<uvos> we are not talking about that
<Wizzup> ok
<uvos> for the x11 backend him needs to switch xcb to a keymap that contains the keysymb it wants to send
<Wizzup> uvos: btw, also with the new radio.img I don't get any signal yet on the d3
<uvos> this irrespective of input language
<Wizzup> ah
<Wizzup> right
<uvos> eg the english vkb contains keycodes not in the us map etc
<uvos> Wizzup: if i read xcb correctly the radio.img just enables the bands nesscary
<Wizzup> xda*
<uvos> yeah
<Wizzup> so the build.proc is the other change required
<Wizzup> prop
<uvos> Wizzup: no you still also need to sim unlock in nvmem, which is something maybe radiocomm can do
<uvos> its 3 things
<uvos> read carefully :)
<Wizzup> I kind of figured I'd just skip that, but since I don't have the modem showing up on leste, I think something is up
<Wizzup> oh am I really that bad
<uvos> you can skip the build proc thing
<uvos> for sure
<uvos> i would install the radiocomm msi you found some while back
<Wizzup> uvos: oh right: 3 - Unlock the phone. This can be accomplished by purchasing the unlock code, and later entering the code upon insertion of a sim card. (T-mobile ATT sim cards will work, but you will get an error saying UNLOCK FAILED, this is NORMAL do not freak out)
<uvos> and see what it says
<uvos> Wizzup: sure
<uvos> we had some more recent version i think
<uvos> but i may be mistaken
<Wizzup> hmm
<uvos> oh no its there
<uvos> 11.12.2
<Wizzup> ah this was with the bionic
<uvos> yeah
<Wizzup> I could just try that ...
<uvos> that just unlocks other bands
<uvos> like radio.img
<uvos> afaik
<Wizzup> hm
<uvos> its unrelated to simlock
<uvos> the bionic wasend certified for gsm by the regulatory agencies
<uvos> the point of tying radicomm is that it has human readable values for the nvmem values
<uvos> so it might be obvious what to do with it
<uvos> we can then later do it with tcmdrw
<uvos> but idk
<uvos> try it :)
<Wizzup> I also see this in my logs:
<Wizzup> 22:37 < tmlind> i also had to do tcmdrw 6850=05 for 3g voice to work properly
<Wizzup> that's not on our wiki anywhere
<uvos> yeah because you wanted to try a voice call with bionic first
<Wizzup> uvos: yeah sure I'll try it, I just have only my gentoo laptop here
<uvos> but we never did it
<Wizzup> so i'll have to install windows and do usb passthrough
<Wizzup> uvos: classic me
<uvos> might work in wine
<uvos> this shows how to use radiocomm in a general sense
<Wizzup> we should really aggregate all these files somewhere
<uvos> YOUR the guy who works at archive.org :D
<Wizzup> I mean on maedevu or something
<uvos> yeah i know
<uvos> still funny that we are so bad at saveing files
<Wizzup> I have a directory with droid3 stuff
<Wizzup> everything I found mostly
<uvos> ok
<Wizzup> also I don't think radiocomm will work in wine really, if it relies on the windows driver for usb
<uvos> yeah i guess not
<uvos> unless it uses the userpace usb facilitys
<uvos> like libusb
<uvos> nah wait
<uvos> its to old for that
<Wizzup> I don't think wine does that either
<uvos> no idea
<uvos> yeah but winusb is to new
<uvos> windows dident have sutch a thing when radiocomm was made i think
<Wizzup> I am cloning the motorola-root-and-rether hack over my lte sim and regret it
* Wizzup stops
<Wizzup> it's very large ;)
<Wizzup> uvos: just to be clear, you said on the xda thread you linked someone said unlock works with radiocomm, but I don't see it
<Wizzup> was it on some page 20 or so? :P
<Wizzup> radiocomm def looks interesting
<Wizzup> heh they are written for windows xp
<uvos> yeah its on p20 or something
<uvos> one guy sais that radiocomm has a field for sim unlocked
<uvos> and he did that but it still dident work
<uvos> so clearly its intended to do this
<uvos> maybe he did soemthing wrong
<uvos> or android was blocking him
<uvos> no or whatever
<uvos> but thats why i would check
<Wizzup> ok, wondering if I go down this road, if I should flash stock radio.img first, and do some dumps
<Wizzup> sounds like I should flash stock radio.img back to at least get android to complain about the unlock code
<tmlind> Wizzup: please take notes on the register id numbers and names if you find something interesting, the same regs should be accessible with tcmdrw too then
<tmlind> no idea what that sim unlock stuff might be, maybe it's not nvram regs
<uvos> maybe its in cal
<uvos> Wizzup: yeah i would save as mutch as possible
<uvos> i would dump the nvmem and dd all partitions mmcblk1p1 to p15
<uvos> to have something to diff against after you sucessfully unlock
<tmlind> so is there some link somewhere about the sim unlock stuff or what's the page 20 above?
<uvos> so for d3 you can buy unlock codes from shady places
<uvos> that work somehow
<tmlind> weird
<uvos> and some guy in the xda thread says that radiocomm has a field for sim unlock
<uvos> but it didnt work for him
<uvos> so we are exploring the avenues
<tmlind> but so where do you type in some code if you get an unlock code?
<Wizzup> tmlind: it was page 6: 13:01 < Wizzup> for the record it's here https://forum.xda-developers.com/t/guide-unlock-xt862-for-t-mobile-att.1406812/page-6
<tmlind> ok
<uvos> tmlind: android
<Wizzup> android has a dialog for it, yeah
<tmlind> ok
<Wizzup> so regarding network unlock, I think it makes sense to flash back the stock radio, see if android still complains about the lock (it should, just to get to default state), and then do various dumps from leste, maybe try the radio image for gsm from the thread above, dump again, and then either look with radiocomm, or if that's too annoying, get an unlock code
<tmlind> fyi, the build.prop changes just update nvram 1877 i think to enable other bands
<Wizzup> ah, check
Twig has quit [Ping timeout: 272 seconds]
<tmlind> nvram 1877 from memory though.. the nvram reg that contains a bitmask of enabled bands
<uvos> sounds like a plan
Twig has joined #maemo-leste
<Wizzup> uvos: want dumps of the partitions at every step too?
<tmlind> maybe droid4 has similar unlock code but no gui to enter it..
<tmlind> Wizzup: tcmdrw dumps before and after unlock code would be interesting
<Wizzup> regardless of radio.img ?
<uvos> yeah
<Wizzup> ok, I'll do it one of these days, maybe wait a day or two to see if others get any more ideas of data they want before I do it
<tmlind> Wizzup: if you reflash radio.img, you need to rewrite the nvram regs for 1877 etc
<uvos> Wizzup: maybe we should have bought that protoype german d4 that was on ebaykleinanzeigen
<uvos> for the raido.img
<tmlind> yeah
<Wizzup> uvos: yeah
<Wizzup> uvos: I guess it's not still there? :p
<uvos> no :(
<uvos> stano_: you dident buy it right?
<tmlind> so if d3 and d4 both have mdm6600, i guess there's a slim chance d3 radio.img can be flashed on d4..
<uvos> i think we tried the same thing with bionic
<tmlind> unlikely though as bionic and d4 have different radio.img keys
<uvos> dident work
<uvos> yeah
<tmlind> yup
<stano_> i did not uvos
<uvos> to bad
<Wizzup> tmlind: right to attempt to make it work in the US you mean?
<tmlind> right
<tmlind> so d3 is xt862 or are there more variants to it?
<uvos> there is milestone 3
<uvos> xt861 and xt860
<uvos> afaik
<uvos> which is the gsm version
<uvos> where the radio.img comes from
<uvos> (specificly the chineese one aperantly)
<tmlind> oh ok
<Wizzup> uvos: oh looks like I ordered a xt861 on ebay, so we could compare
<uvos> great
<tmlind> is there a link to the chinese xt860 radio.img somewhere?
<tmlind> i'll try to flash it on my d4
<Wizzup> there should be chinese firmware I think
<buZz> oh, could we put those codenames on the wiki aswell?
<buZz> XT894 etc
<buZz> instead of only 'masarati'
<Wizzup> looks like it's a regular phone though
<buZz> or next to
<Wizzup> buZz: feel free
<buZz> tnx
<uvos> Wizzup: verhandlungsbasis
<uvos> aka name a price
<tmlind> bbl
<Wizzup> uvos: hm the internet seems to say that unlock codes are only required if you're in the us
<Wizzup> ah, no, nvm
<Wizzup> misreading
inky_ has joined #maemo-leste
inky has quit [Ping timeout: 252 seconds]
<buZz> the droid3 doesnt have a wiki page yet, right?
<buZz> i did the droid bionic and droid4 pages anyway
<buZz> XT875 and XT894
<Wizzup> buZz: I will make one later yes
<sicelo> stano_: you were saying DCEW says "Invalid command" for the command you were using. I'd like to ask if the command itself did work - iirc you were trying to set brightness - was that working through DCEW, or it didn't run at all?
<stano_> hi sicelo, i now set brigness as root with 'echo'
<sicelo> right. i still would like to know if it was working though :)
<stano_> the complete brokenness was the result of tape over the light sensor
<stano_> it's still on-deterministic how bright i get the backlight using the applet
<stano_> *non
<sicelo> alright. let me boot vm to test DCEW
<stano_> this is interesting. using barrier and a mousepointer, i get deterministic brighness when clicking each of the 5 bars. but tapping screen with finger, it's 'random' result
<Wizzup> yes, we know it's a mce problem afaik
<Wizzup> uvos: btw given what I currently have working, it looks like kexecboot might be a better choice than clownboot, or not?
<buZz> -clown- boot? :D :D
<buZz> isnt that kexecboot?
<Wizzup> mhm I guess..
_uvos_ has joined #maemo-leste
<_uvos_> Wizzup: clownboot is an alternative to tmlinds utagboot
<_uvos_> not kexecboot
<_uvos_> aka they both exist to start kexecboot
<_uvos_> aka they both exist to start kexecboot
<_uvos_> if you have a sane dts yeah clownboot is the nexy step
<Wizzup> ok
<Wizzup> btw: tcmdrw --all should work, no?
_uvos__ has joined #maemo-leste
<_uvos__> buZz: yeah i called it clownboot because kexecing from linux to linux in order to kexec linux is clown-y
_uvos_ has quit [Ping timeout: 276 seconds]
<buZz> :D
_uvos__ has left #maemo-leste [#maemo-leste]
inky_ has quit [Ping timeout: 265 seconds]
inky_ has joined #maemo-leste
Twig has quit [Remote host closed the connection]
Twig has joined #maemo-leste
<stano_> are these projects https://github.com/maemo-leste-extras apt-gettable? e.g. crazyparking?
<stano_> 'https://pkgmaster.devuan.org/merged beowulf Release' no longer has a Release file. confuseing me
pere has joined #maemo-leste
<buZz> stano_: thats a wrong url
<buZz> should be deb.devuan.org
<buZz> not pkgmaster.devuan.org
<stano_> ty
<buZz> stano_: -some- of those -extras are apt-gettable
<buZz> but not all
<stano_> i still don't understand Wizzup's sdl1.2 fix. but it works now.
<stano_> i'm just a dog that is happy there is food in the bowl.
pere has quit [Ping timeout: 240 seconds]
<buZz> :)
<stano_> do you have a libsdl1.2 tree compiled on d4 buzz? what do you get with ./testblitspeed --screen ?
<buZz> i have not
<stano_> it might be good to add a fullscreen mode to testblitspeed.c
<stano_> https://github.com/maemo-leste/libsdl this seems to have none of anyone's changes
<sicelo> does anyone have commands they feel should be shipped with Desktop Execution Widget? I'm preparing to update it by removing Fremantle's obsolete commands, and changing the way it handles commands that don't return a value (issue #558)
<stano_> yay thanks
<buZz> :)
<buZz> sicelo: i havent tried it as i barely understood what its for
<stano_> could do something like cat your temperature sensor on every desktop update
<buZz> doesnt conky work?
<sicelo> it does
<sicelo> DCEW is a desktop widget for 'one-shot' commands. the defined commands run only when the widget is tapped, or some other condition specified in the widget is satisfied. conky is always running
<stano_> i think it's a great addition
<sicelo> what?
<stano_> DCEW
<stano_> very nice to be able to put commands on shortcuts
<sicelo> ah, right
<sicelo> there was also a more popular one with more features, Queen Beecon Widget - but i liked DCEW for being more compact and simpler
<stano_> but i'd do some shortcuts to things like set my default gateway, or brightness, or other stuff
<stano_> like one button to setup usb network. that'd be nice
<sicelo> yes, DCEW allows you to do that, you can have multiple widgets (unlike some other widgets where you can have only one of each type)
<sicelo> i'll ship the update without any new commands - i guess people will have differing needs
<stano_> i can't think of anything useful-for-most-people
<sicelo> yeah, me too
<stano_> barrier is very fun. have you tried that? pc mouse and desktop on your leste device
<sicelo> anyway, only few use it, so - keeping it simple
<stano_> yes
<buZz> stano_: i've used x2x for similar
<buZz> ah barrier is a synergy fork
<lel> sicelo closed an issue: https://github.com/maemo-leste/bugtracker/issues/558 (desktop-cmd-exec: does not execute commands that do not return values)
<sicelo> stano_: updated DCEW is in repos.
<sicelo> you may want to look at my comment to your GH issue
<stano_> sudo dsmetool -k /usr/bin/hildon-home && sudo dsmetool -s /usr/bin/hildon-home << can also pick-up other packages installed and show them in menu?
<sicelo> i am not aware that there are bugs with display of newly installed packages in the application menu. the problem only affects widgets, to the best of my knowledge
Twiggy has joined #maemo-leste
Twig has quit [Ping timeout: 252 seconds]
Twiggy has quit [Quit: Leaving]
<sicelo> it's so nice using the VM now that kvm works on my laptop :-)
<stano_> for faster compiles?
<sicelo> maybe it was the hexagonal "theme" that made me avoid QBW on Fremantle - https://wiki.maemo.org/Queen_BeeCon_Widget
<sicelo> stano_: yes, but the compiles weren't really too bad. it was using the 3D accel that was excruciating. i didn't mind too much because i generally am patient :p
<sicelo> and of course, had no other choice anyway, at the time
<sicelo> but yeah, QBW has far more features - maybe should port it one day
<stano_> can opengl-es take a 16-bit color texture and display it on 24/32bpp xorg doing the conversion in gpu?
<stano_> drnoksnes does 16bpp colors internally
<stano_> i'll try to get the simple hildon animation actor test program to run in 24bpp first
<stano_> or maybe not, i don't know the right way to approach it
inky has joined #maemo-leste
inky_ has quit [Ping timeout: 250 seconds]
inky has quit [Read error: Connection reset by peer]
inky has joined #maemo-leste
BenLand100 has quit [Ping timeout: 258 seconds]
<stano_> gprof yields too big binary? - illegal instruction
<stano_> valgrind not available except on aarch64
<stano_> oh it is available if you use http not https for the repo
<stano_> valgrind --tool=callgrind also seems heavy: ==15588== brk segment overflow in thread #1: can't grow to 0x484e000
<stano_> i'd like to see where this program spends its time
<stano_> there used to be this -oprofile thing.. hm
inky_ has joined #maemo-leste
inky has quit [Ping timeout: 265 seconds]
inky has joined #maemo-leste
inky_ has quit [Ping timeout: 258 seconds]
uvos has quit [Remote host closed the connection]
inky has quit [Remote host closed the connection]
inky has joined #maemo-leste