<huckg>
ok, thanks, i will install that and continue later, have to go to work now.
huckg has quit [Quit: Client closed]
<Wizzup>
maybe he can just get deb from newer debian?
wunderw has left #maemo-leste [#maemo-leste]
wunderw has joined #maemo-leste
<bencoh>
I don't remember using a newer fastboot for droid4
wunderw has left #maemo-leste [#maemo-leste]
<bencoh>
why is that different for bionic?
<Wizzup>
uvos: any idea how I can git am your mail to linux-omap?
<Wizzup>
just copying the body of the email isn't enough
<Wizzup>
ah I had to copy the headers as well
<Wizzup>
uvos: hmm your three rfc patches do not seem to apply on top of each other
<Wizzup>
uvos: wait
uvos has quit [Ping timeout: 256 seconds]
<Wizzup>
uvos: yeah the third patch gives me 'corrupt patch' no matter what I try
<tmlind>
uvos: looks like you're mostly done with the led patches
<tmlind>
mighty17[m]: the mmc quirks are only needed on few broken devices, should not be needed otherwise, you may have other issues like unconfigured regulator if not detected
pere has quit [Ping timeout: 240 seconds]
<mighty17[m]>
<tmlind> "mighty17: the mmc quirks are..." <- It just doesn't work on a cold boot
<mighty17[m]>
I don't understand what's wrong
<mighty17[m]>
If i boot into twrp first and then reboot to mainline nmc5 works
uvos has joined #maemo-leste
<mighty17[m]>
mmc5*
<uvos>
tmlind: wich ones?
<Wizzup>
uvos: could you maybe send me the third hp patch again
<Wizzup>
I can't get it to apply without patch or git am complaining
<uvos>
Wizzup: ok
<uvos>
tmlind: do you remember the commit id of the motorola patch that worked around an idle bug in the firmware
<uvos>
that we considerd as the cause of the d4 reboots in the 5.10 era
<uvos>
but was patched in firmware at some later time so was unessecary
<uvos>
i wonder if im wondering if maybe since xt860 was never updated by moto if this problem is the cause of the extra reboots
<uvos>
ah i see the problem
<uvos>
the patch got wraped to 75 lines somehow
<uvos>
wierd
<uvos>
its resent
<uvos>
bencoh: there is a range of versions of fastboot with a bug that causes it to fail with mbm
<uvos>
on all devices
<uvos>
you probubly used a version old enough
<bencoh>
ah
<Wizzup>
uvos: this one applies fine, ty
<Wizzup>
freemangordon: did you test with CMA of 16 or 24 MB?
<uvos>
looks like xt862 has 1.3.5 R2 vs d4's 1.6.4 R2
<uvos>
so this sounds very possible
<tmlind>
yeah might be
<tmlind>
uvos: you had some test case of playing some music for that bug i recall
<Wizzup>
yeah that was a good way to trigger it for me
<Wizzup>
but the droid3 hangs much more often and it's pretty easy to trigger
<tmlind>
ok
<uvos>
tmlind: yeah playing high bitrate music via mpv hanged it pretty reliably
<uvos>
tmlind: the d3 hangs so often it dosent matter tho
<uvos>
im testing the patch right now
<uvos>
tmlind: btw is there some debuging function that would allow me to pin regulators on without chianging dts?
Boshtannik has joined #maemo-leste
<Boshtannik>
Hello!
<Wizzup>
hi hi!
<Boshtannik>
I'm new!
<Boshtannik>
Have found maemo leste os, and remembered that I had my lovely rx-51 phone, that helped me learn programming. So I bought a new one, and put leste on it!)
<Boshtannik>
I'm happy, that this os is still Live!
<Boshtannik>
Thanks to all of you, guys!
<Boshtannik>
Can someone help me?
<uvos>
whats the problem
<Wizzup>
Boshtannik: great to hear
Boshtannik has quit [Ping timeout: 256 seconds]
<Wizzup>
interesting, n900 now uses more pm when off more is enabled, probably another subsystem that goes nuts
<uvos>
i think the d3 stopped hanging
<uvos>
at least i hasent lived this long before
pere has quit [Ping timeout: 256 seconds]
elastic_dog has quit [Quit: elastic_dog]
elastic_dog has joined #maemo-leste
<Wizzup>
uvos: that'd be great
<Wizzup>
uvos: with tony's patch?
<uvos>
Wizzup: yeah
<Wizzup>
ok, shall I apply it to the 5.15 tree then?
<uvos>
Wizzup: im not sure it helps yet, but it cant hurt either
<uvos>
Wizzup: since the vendor kernel contains this patch
<uvos>
so if you like for testing
<Wizzup>
if it doesn't hurt d4 :)
<uvos>
both vendor kernels contain it
<uvos>
solana/maserati
Boshtannik has joined #maemo-leste
<Wizzup>
ok
<Boshtannik>
I guess that default layout is English. And I do have English symbols but adapted to the Russian keyboard.
<Boshtannik>
And spec symbols of software layout does not match to the marks of physical one.
<Boshtannik>
Here is my problem.
<Wizzup>
ah..
<Boshtannik>
I still want to use this phone as learning pocket machine.
<Wizzup>
so there are a few things: I haven't gotten hildon input method to actually switch keyboard layouts yet (with X/xkb), and perhaps we lack the keymap for your specific physical layout
<Wizzup>
do you have a schematic or photo? maybe we can get the files from old fremantle nokia
<Boshtannik>
But can not type free for example in vim, or monodevelop caused by for example semicolon... Just red your new message.
<Wizzup>
(I will be away from the keyboard for a bit, please stick around tonight or tomorrow and we'll be able to fix it)
<Boshtannik>
Yes, I can send you.
<Wizzup>
great
<Boshtannik>
Telegram?
<Boshtannik>
Or how I can send it to you?
<Wizzup>
does email work?
<Wizzup>
spam1@wizzup.org
<Boshtannik>
Yea.
<Boshtannik>
OK.
<Boshtannik>
Have it sent.
<Boshtannik>
God damn it could be awesome, if it would be ported to fxtec pro phone, or for some tv sticks. Hiddon is exactly made for those.
<uvos>
tv sticks? not really hildon has exactly zero keypad naviagion
<Boshtannik>
For the fun, I,ve compiled python 3.10, but could not write programs there, because vim requires lot of special symbols to operate with it.
<Boshtannik>
I am about the simplicity of the interface)
<Boshtannik>
It is comfortable.
<Boshtannik>
Yet more hidden things for special symbols in my default maemo on phone. I could double press blue arrow on left side of keyboard, and I then I had special menu opened with special symbols there. Because there was a lot of them, it had multiple pages.
<Boshtannik>
I believe they are exists in the default os, and could be ported from there.
<Boshtannik>
It is better to say - guess)
<uvos>
that menu exits in leste
<uvos>
it might be temporarly broken
<uvos>
also it only works on gtk2 applications
<Boshtannik>
Hmm, tomorrow I ll try.
<Wizzup>
Boshtannik: thanks for the layout, I got the email
<Wizzup>
we are also looking at (eventually) doing the fxtec port
<Wizzup>
I will be away for most of the evening but I will search for fremantle keyboard layouts tomorrow
<Boshtannik>
Thanks to that phone, and to n-team iam a developer now, and maybe I could help with some testing on my n900.
<Boshtannik>
I would like to write some gui app, for example for fm transmitter with using of the kivy framework, or just tkinter.
<uvos>
the fm transmitter dosent work on any device atm
<Boshtannik>
Better would prefer kivy.
<Boshtannik>
O_o
<sicelo>
isn't kivy going to be heavy on N900?
<Boshtannik>
I guess I saw somewhe on the YouTube, that some guy had it run on his leste.
<sicelo>
and FM transmitter does work on N900 ... if it doesn't, will likely be a trivial fix, as it was working before
<Boshtannik>
sicelo: I do not know
<uvos>
it dident when i tried
<uvos>
but maybe
<uvos>
i mean leste runs on more devices than n900
<uvos>
all of which have way more resources than it
<Boshtannik>
It is only touched driver for sound card?
<Boshtannik>
Ahh, gou you.
<uvos>
but no idea how heavy kivy is
<Boshtannik>
It could be run with opengl
<Boshtannik>
Believe gles 2
<uvos>
sure but n900 is still very very slow
<Boshtannik>
But not sure if the drivers are on leste.
<uvos>
opengl works
<uvos>
gles
<uvos>
but its very slow
<uvos>
compeard to modern expectations
<Boshtannik>
I do not want to bare it.
<Boshtannik>
This phone is still amazing for me.
<uvos>
anyhow im not saying that kivy will be to slow, qml is suprisingly sortof tolerable on n900
<Boshtannik>
I have deployed there some django server, using yggdrasil mesh client on it.
<Boshtannik>
I have tried it once to be installed with just pip install kivy, but did not succeed with run of simple dummy app, it was argued, believe, on lacking compiled option to be run on gles, I guess, that because it was no gles driver there.
<Boshtannik>
It was about 1,5 yrs ago.
<Boshtannik>
Do not know how is it now.
<Boshtannik>
So I could not run spec symbol menu in my terminal app. Please correct me if I am wrong.