orivej has quit [Ping timeout: 240 seconds]
<craige> Well, may exist :-D
<samueldr> >> The Volla OS is based on the Android Open Source Project
<samueldr> well, just another one of those "privacy enhanced" AOSP derivatives
<samueldr> like /e/
<craige> Yep but I thought as a potential hardware target, when the phone exists :-)
<samueldr> hopefully less /e/vil than /e/
* samueldr is searching for a link
<craige> FYI: early adopter PinePhone is on it's way too.
<samueldr> ugh, mediatek that volla phone
<samueldr> so depending on that business, the relevant OSS stuff might not be released
<gchristensen> hm
<craige> wow, quite evil :-)
<gchristensen> this raspberry pi is running quite hot given the circumstances
<samueldr> >> Freedom includes freedom of choice. Therefore you as a supporter should decide with a survey which operation system you prefer:
<samueldr> gchristensen: pis since the 3 are hotter than a $2 pistol
<samueldr> so yeah, given that sentence, it gives more hopes about the software being released
<gchristensen> yeah but its running at 30C above ambient ...
<samueldr> curious if Volla has approached Nemo Mobile and "Ubuntu Touch"
<samueldr> (Ubuntu Touch is not a thing anymore...)
<samueldr> (it's ubports)
<samueldr> but could also be screenshots on the display
<samueldr> I hate having so much cynicism about those projects, but when it's "just an MTK phone" with "just a non-descript AOSP fork", it starts at a wrong place for me
<samueldr> if at the very least they started from a known AOSP fork
<samueldr> >> the Volla Phone comes with a pre-configured VPN
<gchristensen> oh no
<samueldr> great, so I'm sending my data to who-knows-where?
<andi-> There is probably a startup somewhere that helps others build new Android startups...
<samueldr> I actually think there is
<samueldr> hmmm
<samueldr> I hate having lost the name of that business
<Acou_Bass> that phone has a bloody notch, that's the most egregious thing
<andi-> aarrgh it has the "made in germany" anti-feature on the volla page. Do not buy.
<gchristensen> anti-feature?
<samueldr> andi-: explain?
<samueldr> sounds like one of those zombie brands like Black+Decker
<samueldr> or Blackberry, Alcatel
<andi-> I worked at enough Germany companies that used that on their marketing slides. It does mean exactly nothing. It might mean they are just trying to up-sell the product.
<Acou_Bass> is that because some people see German built to mean extra robust/ well engineered etc. so people now use it as a marketing line?
<andi-> yeah
<samueldr> I don't know where in OEM and ODM kind of ladder they are
<gchristensen> lmao.
<samueldr> but Xiaomi seems to work with them at some level
<samueldr> AFAICT likely the factory for the redmi note 7
<samueldr> if not outright a design that has been bought
<Acou_Bass> interesting
<samueldr> willing to bet there are other similar invisible companies in the ladder floating around OEMs
<samueldr> and not talking about one like TCL, TCL is the definite OEM behind Alcatel and Blackberry phones
<samueldr> but thinking they might be using the services of some similar faceless companies
<samueldr> not that there is inherently an issue with that
<samueldr> just like there is not inherently an issue with system76 using clevo design (in the past, if they don't still)
<andi-> There more I spent thinking about Android and the more issues I am running into with my ungoogly Android I just want to buy an iPhone every 6ys and be done.
<samueldr> I don't know whether that would solve your problems :/
<samueldr> (like, really don't know)
<craige> I want to be part of a Google / Apple free world. I'm happy to take th epain so I may make it easier of others in the future.
<andi-> samueldr: I also think I'd be deeply unhappy after the initial hype curve. Somehow society started to build requirements on Android/iOS on everyday life... Like buying a bus ticket only being possible with an App or a vending machine 1km away.
<samueldr> yeah
<samueldr> that's infuriating
<samueldr> I'm sure the moment I'll start dogfooding Mobile NixOS, and gripe about that, I'll be told to shut up and just use Googleful Android
<samueldr> or something like "here's 50¢, get a real phone"
<andi-> Another nice thing I noticed is how Google Maps now has the monopolgy on routing. They show the wrong address of branches when you share an exact location…
<samueldr> heh!
<samueldr> google maps' routing was terrible in Vienna for me
<samueldr> * for walking
<andi-> I wanted to meet with someone at a coffee shop in SFO. I used the address from the link they gave me. Turned out to be the registration address of the company and not that specific shop we wanted to meet at.
<andi-> And there was no way to get the address out of there other then looking at the image of the map and extracting the street name.
<craige> Open Street Maps is woefully incomplete for where I live and I've not been able to find a reliable source of data to upload :-(
<samueldr> (cynical) I'm thinking that no one *can* walk to places on the google maps team... in a walker-free city
<qyliss> I think you're not supposed to upload raw data to OSM generally
<qyliss> Because of licensing
<andi-> Anyway, no reason not to try to run free (as free can be) software :-)
h0m1 has quit [Ping timeout: 246 seconds]
h0m1 has joined #nixos-aarch64
LnL has joined #nixos-aarch64
LnL has joined #nixos-aarch64
LnL has quit [Changing host]
fooker has joined #nixos-aarch64
chiefgoat has joined #nixos-aarch64
<samueldr> it's dumb, but it tickles me in a good way to see fbterm at boot on Mobile
<samueldr> mostly unneeded, but appreciated, sphalerite++
<{^_^}> sphalerite's karma got increased to 75
andi- has joined #nixos-aarch64
<louipc> samueldr++
<{^_^}> samueldr's karma got increased to 133
orivej has joined #nixos-aarch64
Acou_Bass has joined #nixos-aarch64
Acou_Bass has quit [Ping timeout: 240 seconds]
zupo has joined #nixos-aarch64
Acou_Bass has joined #nixos-aarch64
Acou_Bass has quit [Ping timeout: 246 seconds]
Acou_Bass has joined #nixos-aarch64
Acou_Bass has quit [Quit: ZNC 1.7.4 - https://znc.in]
Acou_Bass has joined #nixos-aarch64
zupo has quit [Ping timeout: 265 seconds]
zupo has joined #nixos-aarch64
t184256 has joined #nixos-aarch64
zupo has quit [Client Quit]
Thra11 has quit [Ping timeout: 252 seconds]
Thra11 has joined #nixos-aarch64
DigitalKiwi has joined #nixos-aarch64
Thra11 has quit [Ping timeout: 245 seconds]
zupo has joined #nixos-aarch64
Thra11 has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
t184256 has left #nixos-aarch64 ["Disconnected: Replaced by new connection"]
t184256 has joined #nixos-aarch64
chiefgoat has quit [Quit: ZNC 1.7.5 - https://znc.in]
chiefgoat has joined #nixos-aarch64
chiefgoat has quit [Client Quit]
chiefgoat has joined #nixos-aarch64
orivej has quit [Ping timeout: 265 seconds]
Thra11 has quit [Read error: Connection reset by peer]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
zupo has quit [Client Quit]
Thra11 has joined #nixos-aarch64
lopsided98 has joined #nixos-aarch64
Thra11 has quit [Ping timeout: 240 seconds]
Thra11 has joined #nixos-aarch64
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Thra11 has quit [Ping timeout: 240 seconds]
Thra11 has joined #nixos-aarch64
orivej has joined #nixos-aarch64
ryantrinkle has quit [Ping timeout: 265 seconds]
orivej has quit [Ping timeout: 245 seconds]
ryantrinkle has joined #nixos-aarch64
orivej has joined #nixos-aarch64
lordcirth has joined #nixos-aarch64
<samueldr> I'm wholly confused now
<samueldr> the framebuffer just works for the pixel 2 (non-XL)
<samueldr> it didn't on the 2 XL... so now I don't know if it's because of other changes in Mobile NixOS or because they differ enough to matter
<samueldr> (after all, one is an LG phone, the other an HTC phone)
louipc has left #nixos-aarch64 ["bye"]
THFKA4 has joined #nixos-aarch64
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<clever> samueldr: but does the serial at least work on both?
<samueldr> I don't have the XL anymore
<clever> ah
<samueldr> though likely to work
<samueldr> as documented
<samueldr> I'm thinking it was external factors, mainly the resolution of the issues I had with udev
<samueldr> now I'm having a "fun" time chasing down an early panic
<samueldr> null deref AFAICT
<clever> [ 0.022120] c0 0 Unable to handle kernel read from unreadable memory at virtual address 00000864
<clever> yeah, that could be a null pointer
<clever> [ 0.022197] c0 0 PC is at _raw_spin_lock_irqsave+0x1c/0x50
<clever> sounds like a spinlock is inside another struct
<samueldr> well, I was thinking NULL because of
<samueldr> [ 0.022176] c0 0 Kernel BUG at 0000000000000000 [verbose debug info unavailable]
<clever> [ 0.022378] c0 0 [<ffffff8bb58c817c>] _raw_spin_lock_irqsave+0x1c/0x50
<clever> [ 0.022381] c0 0 [<ffffff8bb46d9844>] wake_up_process+0x14/0x20
<lordcirth> samueldr, how is the PBP image coming?
<clever> [ 0.022386] c0 0 [<ffffff8bb46ca93c>] kthread_create_on_node+0xc4/0x1b8
<clever> [ 0.022391] c0 0 [<ffffff8bb4c17710>] tty_buffer_init+0xa8/0xf0
<clever> the tty may be null?
<samueldr> lordcirth: haven't looked at it further than u-boot yet
<samueldr> lordcirth: busy week-end, and now work :)
<clever> samueldr: i think the 0000000000000000 you saw, is because of a lack of debug info
<samueldr> clever: ok, though I was looking into that, trying to get more debug info
<clever> samueldr: you want to look into the backtrace on 179-187
<samueldr> yes I know that
<samueldr> and it matches with the enabled options
<samueldr> when I enable ttys :)
<clever> samueldr: there may be tools to take a vmlinux file, and the addresses from the dmesg, and reverse lookup line-numbers
<samueldr> though a cursory git diff on the tty stuff shows nothing special from that tree compared to mainline
<clever> samueldr: or just `objdump -d` to disassemble it yourself, and lookup that line#
<clever> there is a flag to intermix assembly and source
zupo has joined #nixos-aarch64
<Thra11> samueldr: Did you (or anyone) manage to get anywhere with mainline u-boot on the pinebook pro?
<samueldr> yes
<samueldr> I had the uefi-based nixos installer image started (but not working) as a test, so u-boot is 100% going fine
<samueldr> the next step was getting that mainline fork going
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<Thra11> samueldr: Cool. I've got the manjaro kernel sources booting, but with the old u-boot. Think I've found the right firmware blobs for the wifi now (hence the question about hardware.firmware), so just baking a new sd-image with that in.
<samueldr> Thra11: then great, with that u-boot you can get mainline~ish everything
<samueldr> u-boot is definitely blob-free
<samueldr> though no gfx init
<Thra11> :)
<samueldr> haven't kept in touch with what other people are doing
<samueldr> so not sure if there's someone working on u-boot gfx init
<samueldr> (which imo is pretty lacking, to release the software that way :/)
<samueldr> (I though that at the very least the BSP stuff would have gfx going)
<samueldr> note that if you want to play with u-boot, the eMMC's u-boot needs to be zeroed, or the internal switch turning the eMMC off
<samueldr> oh, it's in the README
<Thra11> I never checked. When the u-boot on the eMMC boots an SD-card, does it chain the u-boot on the card or just skip to the kernel/initrd?
<samueldr> it doesn't boot another u-boot, it directly handles it
<samueldr> directly handles loading from sd card, the kernel and stuff
<Thra11> Ah ok. Makes sense.
<Thra11> It's a pain having to open and close the case to flip the switches.
<samueldr> yep
<Thra11> I mean it makes sense with it being a laptop, not a dev board
<Thra11> But the fact you can't do a test boot with the bottom off is a bit annoying
<samueldr> would have been neat a hatch, or something, but reduces the solidity of the device, and adds costs
<samueldr> though, something that could have been neat is to put a tactile button at the end of the audio jack, if the audio jack is open ended
<Thra11> I considered cutting a hole, but I think I'd regret it in the long term
<samueldr> yeah, it's likely
<samueldr> depending on how it goes, when I actually start doing more stuff, might pierce the smallest possible hole near the reset and/or maskrom buttons
<samueldr> and cover it with tape when unused
<Thra11> I don't know if they're planning to do bits as spares, but if they did, you could have a 'dev' bottom panel with access holes and a separate 'nice' bottom panel for the rest
<samueldr> AFAIK yes
Acou_Bass has quit [Ping timeout: 250 seconds]
Acou_Bass has joined #nixos-aarch64
Acou_Bass has quit [Quit: ZNC 1.7.4 - https://znc.in]
Acou_Bass has joined #nixos-aarch64
v0|d has joined #nixos-aarch64