belcher_ has joined #maemo-leste
belcher has quit [Ping timeout: 245 seconds]
ceene has joined #maemo-leste
<kshatriya> this article describes (perhaps) what is done to get usb OTG host mode working, while charging both host and peripherals with external power https://blog.workshoptwelve.com/2019/01/04/otg-usb-charge-hub-wtf/
jeramiah has quit [Ping timeout: 268 seconds]
joerg has quit [Killed (tungsten.libera.chat (Nickname regained by services))]
joerg has joined #maemo-leste
sixkxbeh has joined #maemo-leste
sixkxbeh has quit [Remote host closed the connection]
xmn has quit [Ping timeout: 276 seconds]
roalyr has joined #maemo-leste
<roalyr> So since we are flashing a microSD card, how does using ML affects its lifespan?
<roalyr> And how large of a SD card would you suggest?
belcher_ is now known as belcher
<parazyd> sdcards are pretty good these days
<parazyd> I mostly use 32G, but even 8 is decent for Leste
<roalyr> Well yes, it is not like we have the luxury of using persistence mode like in MX linux with that amount of RAM.
<roalyr> Looks like I am stuck at "fastboot flash mbm allow-mbmloader-flashing-mbm.bin" step.
<roalyr> Terminal output is: "target didn't report max-download-size
<roalyr> And it is staying at sending 'mbm' (512 KB)...
<roalyr> Fastboot returns the devices list though.
<sicelo> kshatriya: looks like complicating things ... I thought d4 can charge and host same time ootb, if I recall what uvos said/tried. At least N900, with its hacky/broken otg dies
<sicelo> *does
<roalyr> Okay, looks like I have to try different USB ports.
<lel> parazyd renamed a repository: https://github.com/maemo-leste/tor-network-applet
uvos has joined #maemo-leste
roalyr has quit [Quit: WeeChat 2.9]
<uvos> roalyr needs to use flash:raw
<uvos> as to why thats nessecary on some d4's no idea, might be old mbm version or a interaction with fastboot version
<uvos> roalyr: if you come back and read the logs please fastboot --version as well as the mbm version (the nummber displayed on device under AP Fastboot Flash Mode in fastboot mode)
roalyr has joined #maemo-leste
<roalyr> What is the way to oem unlovk D4?
<uvos> you cant
<uvos> the bootloader is permanently locked
<roalyr> So how do I even flash it?
<uvos> we use a vunerability in the boot process to essentally boot a second bootloader
<uvos> thats unlocked
<roalyr> In my case flashing mbm hangs and doesn't proceed.
<uvos> plase provide the information above
<uvos> please insure the the allow-mbmloader-mbm.bin is free from defect
<uvos> its md5sum should be 8875e9a9860522aa99568b15896fa076
<roalyr> It is as such.
<uvos> plaase provide the information requested above
<roalyr> Which one? Please re-send the message.
<uvos> [09:16] <uvos> as to why thats nessecary on some d4's no idea, might be old mbm version or a interaction with fastboot version
<uvos> [09:18] <uvos> roalyr: if you come back and read the logs please fastboot --version as well as the mbm version (the nummber displayed on device under AP Fastboot Flash Mode in fastboot mode)
<roalyr> Fastboot (Xubuntu 20.10): 1:8.1.0+r23-8
<roalyr> AP: 0A.77
<uvos> thats really old
<uvos> (fastboot, mbm is fine)
<roalyr> I see, got it from standard repo.
<uvos> i use 30.0 and this works fine
<uvos> if the fastboot version is not it, then i dont know why some d4s react differently
<uvos> in this case you have to use flash:raw
<uvos> but i dont reccomend this
<uvos> as it skips some checks and you are flashing a bootloader
<uvos> with obvious bricking implications
<roalyr> Let me try the new fastboot first.
<roalyr> It worked!
<uvos> yay
<roalyr> Phew. It would have been depressing to get a brick that fast.
<uvos> tmlind: ^^^^^ could you please add a note to kexecboot instructions that at least fastboot v30.0 is needed
<uvos> clearly some old versions have issue with mbm
<roalyr> Yay, all good.
<roalyr> BTW, that means I could also flash some more modern android-based OS too... Brings me nostalgic memories of custom ROMs.
<uvos> the maximum is android 7.0, mostly because no one cares you could run android 11 on the mainline kernel
<uvos> or 12 even
<roalyr> I'd stick for 10.
<uvos> well you would have to build it yourself
<uvos> but in theory it should work
<roalyr> I guess.
<roalyr> It loads ML!
<uvos> great
<roalyr> what browser should I get?
Pali has joined #maemo-leste
<uvos> firefox-esr
<uvos> and then set some evvars to allow thumb scrolling
<uvos> and customize the ui a bit
<uvos> works really well
<roalyr> Is there home folder?
<uvos> roalyr: ?
<uvos> maemo leste is just debian
<uvos> so yeah
<roalyr> As in for user files.
<uvos> there is /home/user
<parazyd> btw. one caveat to setting Android useragent is that it blocks you from installing certain plugins
<roalyr> That's fine.
<roalyr> How is battery calibrated?
<roalyr> And how is virtual keypad called?
<roalyr> Oh, figured out thaa it pops up when physical is not deployed.
<roalyr> Okay, the most important question - how to disable auto-rotation to prevent graphics from dying?
<uvos> graphics should not die on rotation
<uvos> on d4
<uvos> what do you mean "die"?
<roalyr> A few rotation and X server (or whatever server) dies and device reboots.
<uvos> this can happen due to a bug in pvr when the virtual keyboard is open
<uvos> otheriwse it never happens to me
<roalyr> I see.
<roalyr> But I'd still switch the turning off.
<uvos> you can download oritation lock applet
<uvos> and activate that
<uvos> (name aproximate)
<uvos> id also recommend the simple brightness widget
<uvos> go apt search for them
<roalyr> Are maemo package mirrors down?
<uvos> no
<uvos> you must apt update first
<roalyr> Oh, I think wifi settinhs didn't work out.
<roalyr> How is it enabled?
<uvos> roalyr: how is what enabled?
<sicelo> Landscape only users are rare. I'm getting curious
<sicelo> roalyr: should be able to bring up the status menu by clicking the time display, then you'll see "Connect" or similar
<roalyr> I am not seeing neither orientation nor brightness applets. Should be restarting, I guess?
roalyr has quit [Quit: WeeChat 3.0.1]
roalyr has joined #maemo-leste
roalyr has quit [Quit: WeeChat 2.3]
<sicelo> Or restarting the status menu ... I don't use those applets, so I don't know what happens when you install them
user1 has joined #maemo-leste
user1 is now known as roalyr
<roalyr> Okay, restarting enabled the notification area applets.
<roalyr> But what about droid 4 symbols on physical keyboard/
<uvos> what about them
<uvos> please be more specific when asking questions
<roalyr> Well, as far as I understand by defauly 'sym' key does not enable the access to the symbols
<uvos> no symb is alt
<uvos> various symbols ar available via ok+ whatever
<uvos> otherwise you can use vkb
<roalyr> there is no alt key.
<uvos> sym==alt
<uvos> caps-lock==shift
<uvos> shift==ctrl
<uvos> on d4 hwkbd
<roalyr> Oh...
<uvos> ok == sym (sorta)
<uvos> ok+p is pipe for instance
<uvos> there are several ok+ for special chars
rafael2k has quit [Ping timeout: 252 seconds]
<roalyr> Well, it seems like there is no straight way to access the symbols then
<uvos> ?
<roalyr> On hw keyboard
<uvos> ?
<uvos> i just told you
<roalyr> Ok dkey does nothing.
<uvos> via ok+ several keys (just try it) you can acess everything
<uvos> ok+o is } for instance
<uvos> and ok+p is |
<uvos> and so on
<roalyr> Doesn't work in my case.
<uvos> run as root
<uvos> udevadm hwdb --update
<uvos> udevadm trigger
<uvos> and then hildon-desktop-rotate-touchscreen.sh as normal user
<roalyr> This did work;:}|
<uvos> parazyd: ^^^^ this still happens
<roalyr> Are the symbols such as plus, underscore, uestion mark mapped
<sicelo> They work as marked. Alt + symbol, I think
<Wizzup> morning
alex1216 has joined #maemo-leste
<parazyd> Besides what is currently in leste-config, we could have an apt hook to run this
<uvos> parazyd: the problem is not apt
<uvos> parazyd: its that it dosent run on first boot
<uvos> udev should update the hwdb on first boot
<uvos> but apearntly it dosent
<uvos> maybe this is caused by the timestamaps from jenkins
<uvos> vrs the d4 which will have its time a 1. jan 1970 innitally on first boot
<parazyd> Can it run in the image build or it needs to be on-device?
<uvos> no
<uvos> it must be on device
<parazyd> ok
<uvos> udev creates the hwdb with info from the kernel
<uvos> running kernel that is
<uvos> parazyd: could we use fake-hwclock to ensure that the system time is after the build time of the image
<uvos> (if that is the problem at all)
<uvos> on first boot
<parazyd> We could, but I had plans to finish reproducible image builds, so this'd break it
<uvos> hmm yeah
<uvos> maybe we should just run it by hand on first boot
<parazyd> We already have an initscript that runs on first boot
<uvos> to force udev to update
<uvos> regardless of time
<parazyd> zzz something
<parazyd> Also hildon-base
cockroach has quit [Ping timeout: 255 seconds]
alex1216 has quit [Ping timeout: 252 seconds]
<kshatriya> roalyr: i added a keyboard layout graphic to the wiki https://leste.maemo.org/Motorola_Droid_4#Notes
<Wizzup> cool
<kshatriya> need to add ` sorry, fixing
cockroach has joined #maemo-leste
<Wizzup> kshatriya: did you see the ones I autogenerated?
<kshatriya> i based it off your post https://github.com/maemo-leste/bugtracker/issues/347
<Wizzup> ok
<Wizzup> ool
<Wizzup> cool!
<kshatriya> i dont understand the * you have on modifier-a
<kshatriya> for soem reason the 'serial cable' entry is to the right of the keyboard picture
<parazyd> Wizzup: Do you want me to implement a shared lib for generating torrc from gconf so it's also usable in icd?
<parazyd> It's be part of the applet repo/package
<Wizzup> I don't know, I'd say no for now since I don't know if I need it
<uvos> kshatriya: loose the left
<uvos> i think
<Wizzup> how about a binary?
<parazyd> There's a bit more generic code there too, so I could make a nice lib
<parazyd> Wizzup: Could do that as well
<parazyd> Then you can actually: gentorrc | tor -f -
<parazyd> Good idea
<uvos> [[File:Maemo-leste-droid4-kbd-2021-07.png|center|620px|thumb|maemo-leste droid4 keyboard]]
<uvos> kshatriya ^^^
<kshatriya> thanks, fixed
<uvos> aemo-leste droid4 keyboard
<uvos> is missing a m
<kshatriya> fixed
<parazyd> It could also be a shell script
<uvos> {{center|maemo-leste droid4 keyboard}}
<uvos> in place of just |maemo-leste droid4 keyboard
<uvos> is supperior i thin
<uvos> k
<uvos> but is ok as is
<kshatriya> [[File:Maemo-leste-droid4-kbd-2021-07.png{{center|maemo-leste droid4 keyboard}}]] doesn't show me a picture in preview
<uvos> [[File:Maemo-leste-droid4-kbd-2021-07.png|center|620px|thumb|{{center|maemo-leste droid4 keyboard}}]]
<kshatriya> that puts a link below pic which says "Template:Center"
<uvos> hmm
<uvos> ok
<uvos> nvm then
<uvos> its not important
<kshatriya> i just noticed ~ tilde is also on OK+z
<kshatriya> unless that's just on mine
<uvos> no
<uvos> thats how it is
<uvos> no idea why
<uvos> probubly a mistake
<uvos> dont document it
<kshatriya> ok
xmn has joined #maemo-leste
rafael2k has joined #maemo-leste
<uvos> ok+z == XK_Next
<uvos> wierd
<uvos> Wizzup: ^^^
rafael2k has quit [Ping timeout: 268 seconds]
rafael2k has joined #maemo-leste
alex1216 has joined #maemo-leste
<kshatriya> this shows off h265 HEVC playback on droid4 nicely (8MB) Axel Borg on his flying chair - doubt he'll mind sharing the video http://0x0.st/-Wta.mkv
pere has quit [Ping timeout: 258 seconds]
roalyr has quit [Ping timeout: 258 seconds]
alex1216 has quit [Ping timeout: 240 seconds]
alex1216 has joined #maemo-leste
u0_a482 has joined #maemo-leste
u0_a482 is now known as roalyr
<roalyr> How to properly calibrate the battery?
<kshatriya> use device until battery is low, then before it shuts off, charge it to full without a reboot
<kshatriya> did you see the keyboard layout graphic i made roalyr ?
<kshatriya> the battery status monitor could have an uncalibrated mode of operation - where it alarms on low voltage and prompts user to charge to full
<kshatriya> but someone would need to code that
rafael2k has quit [Ping timeout: 252 seconds]
<roalyr> Sorry, couldn't keep up, on a lunch in between work now, gotta run soon again. I've explored the Ok+ combos, alas couodn't find the +, ?, * symbols.
<kshatriya> plus is shift =
<kshatriya> asterisk is shift 8
<kshatriya> question mark is shift /
inky has joined #maemo-leste
inky_ has quit [Ping timeout: 276 seconds]
u0_a482 has joined #maemo-leste
roalyr has quit [Ping timeout: 258 seconds]
<u0_a482> By the way, is hardware acceleration possible? Tried to run a few applications and it outputted that omapdrm_dri is not found. I presume that's the case for a missing mesa library?
<u0_a482> Or is there more to it?
<Wizzup> hardware accel for what?
<Wizzup> opengl?
<u0_a482> Yes.
<Wizzup> opengl|es accel is there and working
<Wizzup> opengl is not supported by the driver but you can look at stuff like gl4es
<Wizzup> (without opengl|es, hildon-desktop would -not- be smooth)
<parazyd> Yeah we have also gl4es but didn't experiment a lot
<u0_a482> So I just ignore that error in terminal?
<Wizzup> u0_a482: no, you might need to do some more work, like ld preload gl4es
<Wizzup> brb
<u0_a482> Okay. Will look into it.
u0_a482 is now known as roalyr
<roalyr> Looks like working things out will get me to learn linux much more deeply.
<parazyd> There might be some upstream commits missing
<buZz> is gl4es apt-getable now?
<parazyd> Yeah, but risky afaik
<buZz> ok, i'll refrain for now then :)
<parazyd> I mean, you can always delete kt
<parazyd> I'd be good if someone tries it out though
<kshatriya> i think sdl will default to opengl if available, not using the -es path
<kshatriya> oh i'm installing and deinstalling it all the time
<buZz> ah hmhm
<buZz> would it force hildon to work through gl4es then?
<Wizzup> no
<kshatriya> no
<Wizzup> gl4es is LD_PRELOAD only
<buZz> then i guess fine :)
<buZz> ahh
<Wizzup> so it really shouldn't affect system wise
<Wizzup> wide
<uvos> gl4es is system wide
<Wizzup> uvos: wait what
<Wizzup> do we install it system wide?
<kshatriya> does it still symlink /usr/lib/arm-linux-gnueabihf/libGL.so to /usr/lib/gl4es/libGL.so.1
<uvos> Wizzup: yes
<Wizzup> hm
<uvos> thats why its risky
<uvos> i breaks things
<uvos> because apps that ignore llvmpipe and use es
<uvos> use gl4es now
<Wizzup> I guess it makes some sense
<parazyd> Yeah the point was to have gl4es to be a replacement
<Wizzup> ok
<parazyd> But we need to use it and experiment
<uvos> we should have glvnd
<parazyd> It was just a oneshot
<parazyd> uvos: We have it
<uvos> and switch to gl4es on demand
<uvos> yeah but gl4es dosent use glvnd atm
<uvos> so you cant switch it in or out
<parazyd> mhm
<parazyd> It needs some love
<parazyd> For Leste we have the newest mesa and glvnd
<uvos> right
<parazyd> That's not yet in buster
<uvos> but glvnd is useless
<uvos> because we dont have pvr or gl4es as glvnd backend
<kshatriya> would it make sense to ask the SDL guys for an environment variable to switch preference of backend GL/GL-es ?
<parazyd> Yeah we need a mechanism for this
<uvos> sdl isent really involved in that
<parazyd> Gentoo has eselect with is something like what we want
<uvos> its the app that asks sdl for gl or gles
<parazyd> (Basically a symlink manager)
<kshatriya> thx uvos i was thinking wrong
inky has quit [Remote host closed the connection]
inky has joined #maemo-leste
alex1216 has quit [Ping timeout: 258 seconds]
inky has quit [Ping timeout: 256 seconds]
inky has joined #maemo-leste
<lel> clort81 opened an issue: https://github.com/maemo-leste/bugtracker/issues/562 (Droid4 5.11 Fullscreen rendering errors working/nonworking tests.)
u0_a482 has joined #maemo-leste
alex1216 has joined #maemo-leste
roalyr has quit [Ping timeout: 252 seconds]
belcher has quit [Ping timeout: 240 seconds]
inky_ has joined #maemo-leste
inky has quit [Ping timeout: 250 seconds]
u0_a482 has quit [Quit: WeeChat 3.0.1]
jeramiah has joined #maemo-leste
rafael2k has joined #maemo-leste
inky_ has quit [Ping timeout: 245 seconds]
inky_ has joined #maemo-leste
roalyr has joined #maemo-leste
<roalyr> How to disable the desktop manager and stay in console?
<uvos> choose the other option in the bootloader
<roalyr> That one just disables the xserver?
<uvos> on bionic yes, on d4 it boots single user mode
<uvos> but you can switch runlevel from there
peetah has quit [Ping timeout: 258 seconds]
<roalyr> Thanks.
<roalyr> How many cycles does it take to calibrate the battery?
peetah has joined #maemo-leste
<kshatriya> this TI driver isn't even reporting GL_VERSION . This breaks mpv's opengl-es detection.
<kshatriya> there is some talk about newer driver for droid4 maybe? with fixes?
<kshatriya> i do get EGL_VERSION = 1.4 build 1.9@2253347
u0_a482 has joined #maemo-leste
<kshatriya> /mesa-demos-8.4.0/src/egl/opengl has some tests
roalyr has quit [Ping timeout: 245 seconds]
u0_a4821 has joined #maemo-leste
u0_a482 has quit [Ping timeout: 265 seconds]
uvos has quit [Read error: Connection reset by peer]
belcher has joined #maemo-leste
inky_ has quit [Ping timeout: 245 seconds]
inky_ has joined #maemo-leste
inky has joined #maemo-leste
inky_ has quit [Ping timeout: 258 seconds]
uvos has joined #maemo-leste
adc has quit [Quit: Lost terminal]
inky has quit [Ping timeout: 265 seconds]
inky has joined #maemo-leste
uvos has quit [Remote host closed the connection]
alex1216 has quit [Quit: WeeChat 2.3]
inky_ has joined #maemo-leste
inky has quit [Ping timeout: 265 seconds]
<Wizzup> uvos: hm I also have a win7 img around here, well, going to make a xp install anyway
<Wizzup> uvos: internet mentions this https://gsmserver.com/sigmakey/ - looks interesting
<Wizzup> (wrt droid 3 unlock)
<Wizzup> not exactly cheap, also needs this https://gsmserver.com/sigma-pack-1-activation/
<Wizzup> I kind of doubt that radiocomm will help with unlocking the sim/network, but at least I'll have it avail for some inspection purposes
<Wizzup> windows xp ie cannot go to firefox website to download the installer, heh
<kshatriya> it's good to minimize one's exposure to that, to a few minutes a day max