<missMyN900>
https://github.com/anthonywong/rtl8723bs "Since Linux 4.12, rtl8723bs has been merged. Therefore, this repo is now obsolete." RTL8723BS driver has been mainlined already :D
<missMyN900>
hmm seems like the Surface 3 itself runs Linux pretty well too, although it is a bit larger (10.8"). May be a bit larger for a ML tablet, I don't know
<missMyN900>
*large
<norayr>
i will need help installing maemo-leste on droid3, people, when you come.
<buZz>
eh ok, did i do something wrong on building kernel?
<buZz>
git cloned, got the right branch
<buZz>
grabbed /proc/config.gz, gunzip, mv config .config, make oldconfig
<buZz>
yet, on booting the build, screen remains black, no sign of life (chargeled doesnt turn on either)
<buZz>
oh, make modules/modules_install perhaps?
* buZz
tries
<Wizzup>
norayr: cute
<buZz>
in drivers/....pvrsgx/ , maybe we dont need to build -all- versions?
<Wizzup>
buZz: what are you tryin to do?
<buZz>
just rebuild d4 kernel
<Wizzup>
norayr: I can try to help with the d3 today or tomorro
<buZz>
Wizzup: i still need to test, but i think my mods on a EB41 battery should get me 10-20% more batterylife
<buZz>
kernelmods*
<buZz>
ah, might have just been missing the modules
<buZz>
Linux devuan-droid4 5.15.2-g0fe205dd861a-dirty #3 SMP PREEMPT Fri Jun 24 03:39:53 CEST 2022 armv7l GNU/Linux
<buZz>
w00t
<buZz>
:) now to recalibrate this '1180 mAh' tested EB41 battery
Pali has joined #maemo-leste
xmn has quit [Ping timeout: 268 seconds]
pere has quit [Ping timeout: 240 seconds]
Livio has joined #maemo-leste
uvos has joined #maemo-leste
pere has joined #maemo-leste
vgratian has left #maemo-leste [#maemo-leste]
vgratian has joined #maemo-leste
vgratian has left #maemo-leste [#maemo-leste]
vgratian has joined #maemo-leste
<buZz>
ehhh shouldnt power_supply/usb and power_supply/battery agree about charging voltage?
<buZz>
it seems the /usb one sticks to 4.2v and not the HV charge voltage i set in /battery
<buZz>
and cant see where thats set at all ... oo , let me check devicetree
<buZz>
hmmf, cant find where its from .. tempted to just replace all 4200000 with 4350000
<buZz>
line 938 on cpcap_charger.c seems to override what cpcap_battery.c sets, perhaps
* buZz
tries
<buZz>
yez, indeed #938
* buZz
charging at/to 4.35v now
<rafael2k>
In PP, we use Mobian 5.15 branch plus some patches ML patches we introduce, like that battery type one, for our battery changing applet work, some modules are built-in in order we can boot without initrd, a pinetab panel module, there are some differences indeed between our kernel and mobian 5.15 kernel
<rafael2k>
and last but not least, I installed mobian here just to test, and it was running their 5.10 kernel line, not really the 5.15 as we do
<rafael2k>
it was some time ago I tested mobian, so may be something changes already, I dunno
Livio has quit [Ping timeout: 246 seconds]
<rafael2k>
I'm tempted to try mainline 5.19 to check how upstreaming is going...
<rafael2k>
read that it might be that the cameras driver have implemented the minimal controls needed by libcamera... I'll see
Daanct12 has joined #maemo-leste
Danct12 has quit [Ping timeout: 268 seconds]
vgratian has left #maemo-leste [Error from remote client]
vgratian has joined #maemo-leste
vgratian has left #maemo-leste [#maemo-leste]
norayr has left #maemo-leste [Error from remote client]
<buZz>
rafael2k: would be supercool to get working cam on d4
<buZz>
cams*
<rafael2k>
buZz: Does it have any v4l driver working?
<rafael2k>
with v4l in place, all the rest is much easier... I'm still struggling with the v4l drivers for proper PP cameras support
<rafael2k>
by proper I mean - having a "one-fits-all" low level camera library, which I think libcamera is the best fit
<rafael2k>
and not by using specific hardcoded low level user land to deal with v4l drivers poorly implemented, as it seems it is the case for PP cameras
<uvos>
no
<uvos>
the d4 rear camera has no working drivers and no documentation of any kind (downstream driver or datasheet)
<uvos>
the front camera is a pretty common chip and has various downstream implementations
<uvos>
omap4 iss also isent in mainline
<rafael2k>
so we have at least with something to start with
<rafael2k>
: )
<uvos>
but there is a driver for that floating around too
<uvos>
rafael2k: sure, but rear camera would be pretty hard
<rafael2k>
how does android implementation works?
<rafael2k>
could it's kernel be used as reference/
<uvos>
its implemented in binary firmware on one of the omap4 m3 cores
<uvos>
the android kernel dosent do anything with the camera at all
<rafael2k>
ow, did not know that, that is bad
<rafael2k>
doing some rev. engineering would be some work...
<uvos>
right
<uvos>
i gues you could alos just use the android firmware, but thats pretty undesirable
<uvos>
it also dose all the image processing libcamera would do on the dsp
<uvos>
ie debayering and color correction and so on
<uvos>
(the m3 cores have a dsp)
<rafael2k>
that is that libhybris or something like this, no?
<uvos>
no
<uvos>
the firmware runs on a different processor
<rafael2k>
shit
<uvos>
its not related to using libhybris
<uvos>
the omap4 has 4 arm cores
<rafael2k>
and so there is just an API to talk to this processor and get the frames?
<uvos>
yes via dma
<rafael2k>
understood
<uvos>
the android kernel just gets the compleated image via dma
<uvos>
the other 2 (non linux) arm cores have access to the omap interconnect
<uvos>
like the main ones
<uvos>
so the firmware gets to drive the omap spi and iss interfaces to talk to the cip
<uvos>
and then just push the final frame into ram
<uvos>
after processing it in the dsp
<rafael2k>
hum, so there is not need for "hardware" debugging, just really software digging with the android right?
<uvos>
if you want to use motorolas firmware sure
<uvos>
but then you have binary firmware running
<uvos>
that can access everything
<uvos>
since it sits on the same bus as the cortex a9 processors linux runs on
<rafael2k>
that is not ideal... but it seems a good starting point
Livio has joined #maemo-leste
<rafael2k>
do you have this blog? I mean, could we decompile it, or debug it in runtime?
<rafael2k>
*blob
<rafael2k>
if it is not thaaaaat big
<rafael2k>
it should be possible to use ida pro or something like this to have a grasp on what it does, right?
<bencoh>
uvos: wait, the M3 handles the CSI part, or just the "ISP"/postprocessing?
missMyN900 has joined #maemo-leste
<uvos>
bencoh: m3 dose everything, essentally android just asks the fw for an image and gets a compleatly processed image back in ram
<uvos>
well not quite
<bencoh>
"not quite"?
<uvos>
it has to ask for the image to post processed in a seperate step
Livio has quit [Ping timeout: 255 seconds]
<uvos>
iirc the fw on the other m3 core dose this
<uvos>
it controles the dsp
<uvos>
(also for video decodeing etc)
<bencoh>
so the a9 handles the mipi/csi?
<uvos>
no
<bencoh>
ah, I see what you mean by "not quite"
<bencoh>
okay
<bencoh>
well then maybe the beagleboard/pandaboard projects would be more helpful than android here
elastic_dog has quit [Ping timeout: 264 seconds]
elastic_dog has joined #maemo-leste
<buZz>
i wouldnt mind a blob on m3 if we can use open shit behind it
<buZz>
like baseband
Livio has joined #maemo-leste
Livio has quit [Ping timeout: 255 seconds]
missMyN900 has quit [Ping timeout: 272 seconds]
Twig has quit [Remote host closed the connection]
pere has quit [Remote host closed the connection]
pere has joined #maemo-leste
Pali has quit [Ping timeout: 256 seconds]
missMyN900 has joined #maemo-leste
<missMyN900>
hmm the Atom tablet is a dead end: the touch screen is not detected at all
<missMyN900>
it doesn't work in Devuan (XFCE) and nothing remotely related shows up in the dmesg output; I have checked twice
<missMyN900>
also grepped for various related terms
<missMyN900>
currently wiping it and will be getting rid of it
<buZz>
gimme
<buZz>
:P
<missMyN900>
shipping would probably be expensive
<missMyN900>
it would be better to buy a T100TA locally as apparently those have good Linux supported including touch screen
BenLand100 has quit [Ping timeout: 244 seconds]
<missMyN900>
buZz: besides it is not really worth it to waste time on such an obscure device. Better to focus on something like a T100TA or a Toshiba tablet, which can actually be found on eBay in a quantity of more than 1
<Wizzup>
we have tablets with socs like the droid 4
<Wizzup>
I think uvos and tmlind were working on one of the last missing pieces
<missMyN900>
but yeah all the reports of hardware issues have scared me a bit and I am not satisfied with the battery life at all
<missMyN900>
so might as well get rid of it while it still has significant value
<norayr>
it downgraded my android from 4 to 2, but in a way i cannot even login and start using it.
<buZz>
iirc its exact same soc
<bencoh>
android 2 ?!
<norayr>
and it did not setup kexecboot.
<missMyN900>
I can use the money to buy a USB LTE modem and a much, much cheaper ML device
<xmn>
missMyN900 yeah. It a great for hacking on, but tough if it's your only phone.
<norayr>
yeah default on droid phones was android 2, then it got an upgrade to 4.
<bencoh>
oh, you mean on droid4
<missMyN900>
it's not my only phone though
<norayr>
no droid4 i was able to setup, wiki info is enough.
<missMyN900>
I bought it for the modem since my home internet can be unreliable
<norayr>
but droid3 wiki info is not great.
<bencoh>
ah
<norayr>
droid3 looks very cool, i like how it looks much more than droid4.
<norayr>
i actually don't like how droid 4, 2, 1 look at all.
<norayr>
but droid3 i like.
<Wizzup>
I can help later this weekend, say 18 hours from now or so
<norayr>
so i got some droid3, apparently it had a crack on the screen, and it was like it was thrown in a bucket with glue. i had to clean it up carefully.
<norayr>
yeah thank you!
<norayr>
that's around 9pm for me, that would be amazing.
<norayr>
i usually sleep at about 3am in the morning. which is now.
<Wizzup>
it's 1am here
<xmn>
missMyN900 ah I see
<missMyN900>
xmn: basically I bought it in a hurry after having only done limited research
<missMyN900>
at first LTE did not work at all so it was useless for its intended purpose
<xmn>
dbl oops
<missMyN900>
it only works with an APN other than the default/recommended one
<xmn>
never buy tech stuff in a hurry :P
<missMyN900>
this was the only time I did that...
<missMyN900>
I always do tons of research
<xmn>
mm..hhh. lol
<missMyN900>
I wish I had discovered the ThinkPenguin USB LTE modem at that time
<missMyN900>
and just bought that
<missMyN900>
I would have discovered ML eventually anyway
<missMyN900>
and probably just bought a DB
<missMyN900>
and it would have saved me money and time...
<xmn>
sell it sooner rather later I would say or hold onto it for when global supplies become worst.
<missMyN900>
it is already out of stock currently
<missMyN900>
it was supposed to be in stock again this month though
<missMyN900>
right now I am already selling other stuff
<xmn>
my n900 is about to get kicked off of tmob :(, so I keep trying to run the PP as my daliy, but too many stoppers.
<missMyN900>
have you tried latest pmOS 22.06?
<missMyN900>
it is very unstable for me
<missMyN900>
but Plasma is faster/smoother than 21.12 SP4/5
<xmn>
Just keep in mind that these items may increase in value as things run out. Look at rb pi's
<missMyN900>
honestly, I am not willing to bet on it
<missMyN900>
I have lost quite a lot of money on phones before
<missMyN900>
niche ones
<missMyN900>
(BB Classic and Jolla)
<xmn>
When I get time I will try the latest of sailfish, Maeno-leste again
<xmn>
meamo-*
<missMyN900>
ML runs quite nicely but there is a regression
<xmn>
lol, nm
<missMyN900>
you cannot trigger HIM anymore with the volume up button
<missMyN900>
I have filed an issue on GH
<missMyN900>
so that limits usability
<missMyN900>
are you on T-Mobile US as well?
<xmn>
it will get fixed, these guys are doing amazing work keeping maemo alive.
<missMyN900>
for sure
<missMyN900>
just giving you a heads-up about the current state
<missMyN900>
since you are trying to daily drive
<xmn>
yeah all the US carries are or have done it.
<missMyN900>
xmn: anyway, if you want to use LTE on the PP on T-Mobile US, the "fast" LTE APN won't work
<xmn>
I will likely daily sailffish on cough android HW :)
<missMyN900>
you need to use "speedtalk" mobile broadband or something like that
<missMyN900>
I think it may be a laptop-oriented APN
<missMyN900>
that is what Plasma autodetects and it works
<xmn>
lte not 4g right?
<missMyN900>
even though T-Mobile recommends "fast" for LTE devices
<missMyN900>
I am not sure
<xmn>
so far the data on the PP and tmob has been really good and stable.
<missMyN900>
are you using Phosh?
<xmn>
I don't have my sim in it right now so can't check.
<xmn>
yeah manjaro & mobian phosh
<missMyN900>
Phosh doesn't have autodetect last I tried
<xmn>
mostly manjaro at the moment since it updates quickly
<missMyN900>
but I only ever tried pmOS
<xmn>
I though mobian does, I would need check
<uvos>
Wizzup: ok so i rebased everything on top of 5.18
<uvos>
everything works except for cpcap/hp patches
<uvos>
not sure why that stopped working, ill take a look later (maybe tomorrow)
<xmn>
I really wanted to like ubports, but in the end it's just not for me. Now if they move lomri over some where else I could try that.
uvos has quit [Ping timeout: 268 seconds]
<xmn>
But I really like (or am used to) the experience of my n900. The only thing that felt as good in some ways was sailfish. So if nemo takes off I could image it could be the ideal DE for me with debian underneath