| Gary_ | I understand...we have no 3g here and the n900 is too pricey with the ability for not making calls | 00:00 |
|---|---|---|
| Wizzup | no 2g either? | 00:01 |
| Wizzup | freemangordon: ok I deleted the acc, rebooted and it came back | 00:02 |
| Gary_ | no 2g here as well, tower companies want everyone on 4g/5g so they can force us to buy their phones...crazy | 00:04 |
| Gary_ | I'm sure 4g will be fading soon as well | 00:05 |
| Gary_ | Japan is shutting down 3g at the end of the month, two of softback phones are now bricks :) | 00:07 |
| Wizzup | that's quite insane | 00:07 |
| moparisthebest | 3g data or only voice? In USA they killed just the voice, you can only make cell calls with VoLTE now | 00:08 |
| Wizzup | I've made 2g/2.5 calls just fine in the us | 00:09 |
| Wizzup | a couple months ago | 00:09 |
| moparisthebest | Maybe there are still areas it works? The carriers all officially dropped it in 2021, delayed a year from the original 2020 date | 00:11 |
| Wizzup | in any case, we do support devices with 4g | 00:12 |
| moparisthebest | That's when I ported my number to jmp.chat to make calls over XMPP, because VoLTE doesn't work on my phone unless I use the stock OS... | 00:12 |
| Wizzup | Supporting the 4g modem on the razr will just be a lot of extra work | 00:13 |
| moparisthebest | You support VoLTE ??? That's different from LTE data | 00:13 |
| moparisthebest | Even lineageos only supports VoLTE on very few devices, OnePlus and some others | 00:14 |
| Wizzup | ifi t works on the pinephone on other oses we can probably support it | 00:19 |
| Wizzup | and I think it does work on the pinephone | 00:19 |
| Wizzup | but I haven't tried | 00:19 |
| Gary_ | It works on the pine just fine, 4g that is | 00:21 |
| Gary_ | even leste shows 4g...:) | 00:22 |
| Wizzup | yeah | 00:22 |
| moparisthebest | But that's data, not calling | 00:23 |
| Wizzup | internet says the modem does it internally on the pinephone | 00:28 |
| moparisthebest | Nice, just not all phones do | 00:36 |
| Wizzup | in general cellular calls just work less well than they used to imo | 00:38 |
| Wizzup | in any case, where I live 3g will be supported for a long time | 00:38 |
| Wizzup | updating jenkins atm.. | 00:40 |
| Wizzup | arno11: also, does the phone vibrate for you upon incoming call | 00:53 |
| Gary_ | The pine/leste supports VoLTE, the 4th column on the second CLCC line confirms it...+CLCC: 2,1,0,1,0,"",128 --(0 for legacy and 1 for VoLTE) | 01:15 |
| gnarface | over on pine64 irc a while ago someone had mentioned the anecdote that after they were able to confirm the late shutdown of their carrier's 3g service, 2g was still functional | 03:00 |
| gnarface | maybe for some legacy emergency hardware in the wild or something, was the speculation | 03:00 |
| gnarface | for a while in the early days of the pinephone that was a known workaround while 4g support was still broken; forcing the modem into 2g mode | 03:01 |
| gnarface | afaik that hasn't been needed for a while though | 03:02 |
| uvos__ | xt912 is in exactly the same boat as droid4 its lte modem will never work besides maybe in some carribian islands as it uses a frequency only used by verizon in us and in us its permanently simlocked to verizon who will not activate it | 09:29 |
| tmlind | Wizzup: so do you have a mass storage usb gadget configured on your device when pluggin the usb cable and the oops happens? | 10:51 |
| tmlind | i'm looking for some reliable way to reproduce oopses with usb if possible | 10:53 |
| Wizzup | tmlind: I think usbnet, that's the default on leste | 11:00 |
| tmlind | ok, and it happens on plugging in the usb cable or at some random point? | 11:01 |
| Wizzup | at some random point while it is plugged in more likely | 11:01 |
| tmlind | ok | 11:01 |
| Wizzup | not necessarily when it is fully charged | 11:01 |
| tmlind | flakey cable or a working usb cable? | 11:02 |
| Wizzup | yeah, so ... I have no idea if this helps but I feel like I've had it more while I was travelling, like when charging in a car or in an areoplane, using the outlets on those transports | 11:02 |
| tmlind | so possibly related to a loose connector and some shaking? | 11:03 |
| Wizzup | could be, or just how the power is generated | 11:03 |
| Wizzup | (if I plug in my earphones to my thinkpad on the airplane I get a nice noise tone) | 11:03 |
| Wizzup | sorry if I don't remember better, I will have to find what I wrote in the log to get a better memory of it... | 11:04 |
| Wizzup | if it happens again I'll try to write up a bit more detailed piece | 11:04 |
| tmlind | so connected to a computer or just a charger? some chargers can send out usb packets too i think.. | 11:04 |
| Wizzup | I don't know if it's just usb packets or not, I would assume it's just a charger, but maybe they do some fast mode negotiation | 11:04 |
| Wizzup | the cables I use aren't power only at least, I think | 11:05 |
| Wizzup | (i.e. they have wires for data) | 11:05 |
| tmlind | or it could be something triggering a bogus usb setup packet | 11:05 |
| Wizzup | right | 11:05 |
| tmlind | usb sniffer would show what goes on if it was reproducable | 11:06 |
| Wizzup | I don't have one of these I fear | 11:06 |
| tmlind | yeah me neither, linux kernel can be used except for signal level tracing | 11:09 |
| tmlind | if it's somehow reproducable when connected to a linux pc | 11:09 |
| Wizzup | It's not really reproducable, I will try to plug into the car again every time (I don't use it often) | 11:10 |
| Wizzup | uvos__: maybe we can apply the fix to our stable kernels as well so that I'd at least have the other fix | 11:10 |
| tmlind | well i only have an old usb1 sniffer which is totally unusable with usb2 issues :) | 11:10 |
| uvos__ | Wizzup: fix? what fix/ | 11:21 |
| Wizzup | uvos__: this weekend tmlind posted a link to fixing a usb oops | 11:28 |
| uvos__ | Wizzup: can you relink it? | 11:52 |
| Wizzup | ok | 11:56 |
| Wizzup | 13:08 < tmlind> Wizzup: so i thought i looked at the usb kernel oops you reported earlier.. but turns out i likely fixed a different oops i had saved | 11:56 |
| Wizzup | 13:09 < tmlind> here's the one i just fixed: https://lore.kernel.org/linux-phy/20240128120556.8848-1-tony@atomide.com/T/#u | 11:56 |
| Wizzup | 13:09 < tmlind> uvos: maybe apply that to the m-l kernel? | 11:56 |
| Wizzup | (sorry for the extra highlight) | 11:56 |
| Wizzup | uvos__: I would like to post a new newspost around or before fosdem | 14:44 |
| Wizzup | uh, so the reason I highlighted you | 14:44 |
| Wizzup | can I use sphone.d to change the sphone loop? | 14:44 |
| Wizzup | like, can I switch to voicecallmgr using leste-config ? | 14:44 |
| uvos__ | not yet | 14:47 |
| uvos__ | i would like to at least test the new system firs | 14:47 |
| uvos__ | t | 14:47 |
| uvos__ | wich needs me to merge the other new code and do a release | 14:47 |
| uvos__ | you can change, the loop module sure but not the ofono->vcm switch | 14:47 |
| Wizzup | ok | 14:48 |
| Wizzup | I want to make a meta pkg for it, but the moment tp-ring is pulled in regular sphone with ofono breaks | 14:49 |
| Wizzup | due to how tp-ring just takes over | 14:49 |
| uvos__ | maybe just patch the poor behavior of ring away | 14:50 |
| uvos__ | its really anoying anyhow | 14:50 |
| uvos__ | or leave ring out for now | 14:51 |
| Wizzup | ring is the essential piece | 14:51 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!