| norly | uvos: thanks! | 00:30 |
|---|---|---|
| norayr | people | 00:48 |
| norayr | i don't know... i have so many questions... | 00:48 |
| norayr | i understand you are busy but i am ignored for several days. | 00:48 |
| norayr | :/ | 00:48 |
| norayr | one question was about the new boot loader entry. | 00:49 |
| norayr | i have read here something about it. and now my droid, today, drained the battery. and i again remembered about my question. | 00:49 |
| norayr | someone mentioned there is a new menu entry | 00:50 |
| norayr | that may charge the droid. and i asked if that menu option is a part of new maemo leste image? | 00:50 |
| norayr | i guess it is not. it is part of that bootloader, kexecboot, i guess was it's name. | 00:51 |
| norayr | so it is separate from the leste image right? | 00:51 |
| norayr | then having a new image won't help me. | 00:51 |
| norayr | another question was about the messages i get when i boot leste. | 00:51 |
| norayr | it tells me to remove /etc/init.d/zram, and deactivate the service. but it also tells that zram situation improved, so i am confused. | 00:52 |
| norayr | i guess that option should be part of droid4-kexecboot.img? | 00:55 |
| norayr | (back to the first question) | 00:55 |
| norayr | if i manage to starte droid, i probably have to backup the home data, and install the new image... to understand everything is right with zram. | 00:57 |
| norayr | but then, will i use data about my wifi access points? where is it located? in my home? or somewhere in /var directory? | 00:57 |
| _uvos_ | norayr: there is no menu option that charges the phone | 08:27 |
| _uvos_ | it should enter a charge only mode if leste is booted with microusb plugged in | 08:28 |
| _uvos_ | but idk if all pieces for that are in non devel | 08:28 |
| _uvos_ | you can alos use androids charge mode too ofc, if needed | 08:29 |
| _uvos_ | idk what your asking about wrt zram | 08:30 |
| _uvos_ | we have that enabled by default and thats fine | 08:31 |
| _uvos_ | unfortionalty the wifi access are stored in gconf | 08:31 |
| _uvos_ | the gconf datastore is in home yeah | 08:32 |
| Wizzup | uvos: https://leste.maemo.org/User:Wizzup/Jenkins | 10:36 |
| norayr | uvos, thank you. let me show you the screenshot about zram. | 12:17 |
| norayr | so i hope if i backup the home, then back it up back to the newly installed system, then reboot, i'll get my wifi data back? | 12:18 |
| norayr | hmm, i cannot make a screenshot. every time i was powering droid on, the browser would appear with the message about update information | 12:20 |
| norayr | and zram part in it. | 12:20 |
| norayr | so when booted leste on droid4 last several times, i got that browser window with recommendation to do with rc-update del zram atd then on the same line, rm /etc/init.d/zram. but wouldn't it just disable tce service? | 12:22 |
| norayr | but before that there was a suggestion to edit zram configuration file. | 12:22 |
| norayr | so i am confused about it. | 12:22 |
| norayr | the info was about april update. | 12:22 |
| norayr | but i cannot find anything like that here: https://maemo-leste.github.io/maemo-leste-sixteenth-update-november-and-december-2021-january-april-2022.html | 12:35 |
| Wizzup | so what is the problem? | 12:43 |
| sicelo | Wizzup: uvos, he is referring to the salutem message that appeared after upgrade. I didn't read it myself, but either norayr got confused by it, or it's confusing to begin with. Someone should review it | 14:52 |
| Wizzup | want to be that person? :) | 14:57 |
| buZz | rsync: write failed on "/home/amprolla/images/droid4/20220417/maemo-leste-1.0-armhf-droid4-20220417.img.xz": No space left on device (28) | 15:04 |
| buZz | https://phoenix.maemo.org/view/Images/job/leste-image-droid4/109/consoleText | 15:04 |
| buZz | i wondered why droid4 image was lagging two weeks | 15:05 |
| buZz | :D | 15:05 |
| Wizzup | yeah. the vm is constantly out of space. | 15:05 |
| Wizzup | we need to migrate the infra to another machine IMHO | 15:05 |
| buZz | need a disk? | 15:05 |
| buZz | ah | 15:05 |
| Wizzup | it's not our infra | 15:05 |
| Wizzup | it's maemo.org infra | 15:05 |
| Wizzup | the I/O is also really really slow | 15:05 |
| Wizzup | so it's better to move to some of our own stuff | 15:06 |
| buZz | hmhm | 15:07 |
| buZz | [35m [00m [01;37m . [00m [22;37mBacking up the entire Internet... [00m | 15:07 |
| Wizzup | but it takes time to do it | 15:07 |
| buZz | ah, that step might take a lot of space | 15:07 |
| buZz | :) | 15:07 |
| Wizzup | and we need to ask the maemo folk to change dns | 15:07 |
| buZz | hmmf, first boot of the 20220410 image, and maemo showed me the 'unlock swiper' once, and then hung and now just rebooted? hmm | 15:15 |
| buZz | i'll leave it on power for a while, hope i can get this fabled 'two day standby' | 15:15 |
| buZz | :P | 15:15 |
| buZz | yeah wtf, battery is 3.2V and leste decides to shut down instantly, instead of going to that 'charging mode' | 15:19 |
| buZz | :( | 15:19 |
| buZz | hmmm yep, its -never- hitting any charging | 15:27 |
| bencoh | I think I have a similar issue, but I'd need to investigate here | 15:28 |
| buZz | omg, it hit 3.3V and continued after ~6 bootcycles | 15:28 |
| buZz | ffs | 15:28 |
| buZz | :P | 15:28 |
| bencoh | (right now mine might be completely discharged actually, I didn't manage to boot it last I tried, I'll have t otry aain with a wallcharger) | 15:28 |
| buZz | wherever that threshold it, i wanna lower it to 3.0 or maybe 2.8 | 15:28 |
| buZz | bencoh: do you have a usb condom? | 15:28 |
| buZz | (only power pins connected through, not data) | 15:29 |
| buZz | there seems to be two results to connecting USB , one is 'get some kinda charge mode' the other is 'haha just boot!' | 15:29 |
| buZz | usb condom can get the second type to change into first type | 15:29 |
| bencoh | I think my wallcharger shorts D+/D- to the ground yeah, I'll have to check | 15:30 |
| buZz | i wonder if other mapphones behave similar on that | 15:31 |
| buZz | and pop, it just rebooted | 15:31 |
| buZz | -_- | 15:31 |
| * buZz assumes it just went under X volt and decided to powerdown, then on 'wrong charger' making it instaboot again | 15:32 | |
| buZz | booted up to hildon, then turned on 'the white LED of powerdown' | 15:33 |
| buZz | lol | 15:33 |
| sicelo | Yes ,d+/- short is also effective on droid4 | 15:33 |
| buZz | sicelo: for which of the two modes i described? | 15:33 |
| buZz | the latter, right? | 15:34 |
| sicelo | But yeah, d4 boot can be heavily influenced by alignment of the planets | 15:34 |
| sicelo | buZz: which two? | 15:34 |
| buZz | 15:29:24 < buZz> there seems to be two results to connecting USB , one is 'get some kinda charge mode' the other is 'haha just boot!' | 15:34 |
| sicelo | I've never seen droid4 wait to charge ... i only always see it boot on usb connected | 15:35 |
| buZz | sicelo: well, i just described how you can see these two different things | 15:35 |
| buZz | read up ;) | 15:35 |
| sicelo | I read. I'm saying I've never seen your first scenario. Or i don't understand it. What do you mean by 'some kind of charge mode'? | 15:36 |
| buZz | this mode is ; droid 4 is powered off, you connect USB and you -only- get a green led for charging | 15:37 |
| sicelo | Never seen it | 15:38 |
| buZz | sicelo: i described how you can get there | 15:38 |
| buZz | after a while it gets into another charging mode where the green led only flashes ~50ms every ~1s | 15:38 |
| buZz | might be some trickle charge, or just a bug | 15:38 |
| buZz | sicelo: TLDR ; 15:29:35 < buZz> usb condom can get the second type to change into first type | 15:39 |
| buZz | 15:28:51 < buZz> bencoh: do you have a usb condom? | 15:39 |
| buZz | 15:29:00 < buZz> (only power pins connected through, not data) | 15:39 |
| buZz | nothing shorted | 15:39 |
| sicelo | I don't have a 'condom 'so maybe that's why I've never seen it. | 15:39 |
| buZz | hmhm ,well try different usb powersupplies? some seem to hit 'mode1' , others 'mode2' | 15:40 |
| buZz | i am not so sure 'mode2' (the booting one) even enables the charger | 15:40 |
| sicelo | Does it get into that mode reliably? I can go through the trouble of making a condom if it's really reliable, otherwise not worth it :-) | 15:40 |
| buZz | yes, both modes are 100% reliable to hit | 15:40 |
| buZz | and i'm kinda sure actually -booting- in 'mode1' makes it 100% unaware any usb powersource is connected | 15:41 |
| buZz | sicelo: i cant say its a reliable way to charge! | 15:41 |
| sicelo | I'll make it then. | 15:41 |
| buZz | i've been having endless troubles getting a 'empty' droid4 to start back up into a charging setting | 15:41 |
| buZz | sicelo: i grabbed the 'newest' <2euro 230V-USB psu from action.com | 15:42 |
| buZz | this one does 'mode1' all the time | 15:42 |
| buZz | and i have the ~3yo model of the <2eu 230V-USB psu from them , which does 'mode2' all the time (and if i plonk a usb condom between, it hits 'mode1' all the time' | 15:42 |
| sicelo | For a quick test, I can cut the data tracks on my power bank that is able to reliably start droid4 in whay you describe as mode2 | 15:44 |
| sicelo | This power bank has shorted data pins | 15:44 |
| buZz | the 'no data pins' mode is mode2 | 15:50 |
| buZz | maybe i should start a wikipage about this? | 15:51 |
| buZz | or a github issue, hmm | 15:51 |
| buZz | i really wish we could get kexecboot to just 'hang' and switch to a charging mode when <x voltage | 15:51 |
| buZz | now booting in 'mode1' , leste detects power on the usb port | 15:52 |
| buZz | (i just got my datasim, trying to test its functionality | 15:52 |
| buZz | eh, leste -did- detect power, at least, green led was on as like charging, BUT, it just randomly rebooted while in hildon and hildon didnt show the charging status | 15:53 |
| buZz | man, what a dance :P | 15:55 |
| buZz | i'm -guessing- the simcard makes the modem startup which draws so much current that leste murders itself :P | 16:01 |
| buZz | maybe i should just dig up a random 'li+ charger' and hook it to the battery terminals | 16:02 |
| sicelo | I'm confused now. I said on d+/- shorted charger, d4 boots up always for me. What I'd like is emergency charging where it doesn't boot. I've never seen this (is cpcap even able to regulate charging without software control?) | 16:07 |
| buZz | i see droid4 now in 'mode1' doing 50mA draw | 16:08 |
| buZz | i dont believe those 50mA are -just- the green led it turned on :P | 16:08 |
| buZz | but, well, very tempted to just hookup 'failsafe charging' | 16:09 |
| sicelo | N900 1-0 Droid4, wrt low battery issues:-p | 16:11 |
| sicelo | For system performance, yeah droid4 is miles better | 16:13 |
| buZz | i dont remember n900 doing much better on this, but havent used millenialPDAs a lot ;) | 16:16 |
| Wizzup | my god I've wasted several hours today trying to get anbox and whatspp to work again | 16:16 |
| Wizzup | this is such a hell | 16:16 |
| Wizzup | now it works but the web sessions are gone | 16:16 |
| bencoh | on pinephone you mean ? | 16:16 |
| Wizzup | vm | 16:17 |
| bencoh | oh | 16:17 |
| bencoh | how did it break? | 16:17 |
| _uvos_ | buZz: so are you on devel | 16:17 |
| Wizzup | the vm fs got corrupted | 16:17 |
| bencoh | ouch | 16:17 |
| buZz | _uvos_: no | 16:17 |
| Wizzup | yeah, and the number I had long lost | 16:17 |
| Wizzup | but yeah anbox has no camera support | 16:17 |
| buZz | i'm on : buzz@h81m:~/droid4$ xzcat maemo-leste-1.0-armhf-droid4-20220410.img.xz | sudo dd status=progress bs=1M of=/dev/sde | 16:17 |
| Wizzup | so no way to scan a qr ... | 16:17 |
| buZz | which is the latest image to have been built | 16:17 |
| bencoh | I still don't have whatsapp because I don't want to end up with people sending me messages, and me missing those | 16:17 |
| _uvos_ | buZz: devel contains several bug fixes related to charging | 16:17 |
| _uvos_ | it wokrs pretty mutch 100% there | 16:18 |
| buZz | _uvos_: ok, i dont have those nor can i get it booted up to even install those ;) | 16:18 |
| _uvos_ | use android | 16:18 |
| _uvos_ | to charge | 16:18 |
| buZz | is there a -devel prefab .img.xz? | 16:18 |
| buZz | my android install is broken since ages | 16:18 |
| _uvos_ | sicleo: yes cpcap is fully hw charging | 16:19 |
| buZz | did we break it then? or just forgot to configure it in the right modes? | 16:19 |
| _uvos_ | its just mbm sets the tresh really low for cpcap to boot with micro usb pluged in | 16:19 |
| buZz | as i cant seem to get any real charging beside the ~50mA through 'unbooted' setup | 16:20 |
| buZz | maybe thats configured for eh , non-battery setups? :D | 16:20 |
| sicelo | Wizzup .. isn't anbox no longer maintained anymore? | 16:20 |
| _uvos_ | buZz: no thats how it works | 16:20 |
| buZz | _uvos_: so, mbm configured the cpcap? to what? | 16:21 |
| Wizzup | sicelo: doesn't matter, it worked | 16:21 |
| buZz | can we change those to work better? :) | 16:21 |
| sicelo | buZz: bq24 can completely handle empty battery with no issues for me. Plus .. you can yank it out easily if you must :-) | 16:21 |
| buZz | eh | 16:22 |
| buZz | not sure what you're saying | 16:22 |
| _uvos_ | cpcap allways trickle charges, it trickle charges because it cant negotatiate for more power via usb by itself (you have to negotiate high power class even for 500mA) | 16:22 |
| buZz | sicelo: you're saying 'your issues dont exist' ? :D | 16:22 |
| _uvos_ | mbm sets the thresh voltage | 16:22 |
| buZz | _uvos_: to what? | 16:22 |
| _uvos_ | to boot | 16:22 |
| buZz | where does it set it? | 16:22 |
| _uvos_ | cpcap registers | 16:22 |
| buZz | line of code? | 16:22 |
| sicelo | I'm saying the pain i experience with d4 is absolutely new to me | 16:23 |
| _uvos_ | mbm is closed sourcep | 16:23 |
| _uvos_ | (its the bootloader) | 16:23 |
| buZz | sicelo: alright, not sure what use that mentioning is then :D | 16:23 |
| _uvos_ | anyhow | 16:23 |
| buZz | _uvos_: are you saying even android users back in the day would suffer this? | 16:23 |
| buZz | the settings are what they used aswell? | 16:23 |
| _uvos_ | yes no | 16:23 |
| _uvos_ | so the problem is | 16:23 |
| _uvos_ | that kexecboot is slow | 16:24 |
| _uvos_ | and mbm thresh is very low | 16:24 |
| buZz | and doesnt enable charger | 16:24 |
| _uvos_ | that was fine | 16:24 |
| _uvos_ | because android booted fast | 16:24 |
| _uvos_ | but our boot takes so long | 16:24 |
| buZz | hmhm | 16:24 |
| _uvos_ | that a battery just over mbm thresh dies | 16:24 |
| _uvos_ | anyhow this is mostly solved | 16:25 |
| _uvos_ | in devel | 16:25 |
| buZz | just not on a image anyone can install ;) | 16:25 |
| _uvos_ | by improving leste behavior | 16:25 |
| sicelo | buZz: i was responding to [16:16] buZz: i dont remember n900 doing much better on this, but havent used millenialPDAs a lot ;) | 16:25 |
| sicelo | Anyway | 16:25 |
| buZz | sicelo: ah, bq24 is relevant to that? | 16:25 |
| * buZz no clue | 16:25 | |
| buZz | :) | 16:25 |
| sicelo | Of course. It's the charging chip. Sorry i thought you were aware | 16:26 |
| _uvos_ | you cant really do any better than cpcap, if the sw is implemented as the booloader expects | 16:26 |
| _uvos_ | without violating usb spec | 16:26 |
| _uvos_ | (which is common tbf.) | 16:26 |
| sicelo | Anyway, with d4, i noticed that sometimes it won't charge when it boots, and doesn't 'see' charger is connected (no green led). | 16:26 |
| sicelo | So now when battery is very low, and it starts booting, i found removing and reconnecting cable at some 'magical' point in time during boot helps | 16:27 |
| _uvos_ | this happens when the low vbus voltage failsafe trips | 16:28 |
| _uvos_ | this is set at 4.2V | 16:28 |
| _uvos_ | also there was a bug (maybe still in stable) that cause this too | 16:29 |
| sicelo | I've never used stable | 16:29 |
| buZz | yeah , plus the '3.2V' threshold | 16:29 |
| buZz | which is way too high | 16:29 |
| _uvos_ | no its not | 16:30 |
| buZz | yeah | 16:30 |
| buZz | it is :D | 16:30 |
| _uvos_ | no | 16:30 |
| buZz | whats the voltage of a empty li-ion ? | 16:30 |
| _uvos_ | 3v | 16:30 |
| buZz | 2.8V indeed | 16:30 |
| _uvos_ | no | 16:30 |
| Wizzup | my droid also often seems to turn off way too soon, esp since I went to asia, and after that I even swapped the batt | 16:30 |
| buZz | not half a volt higher | 16:30 |
| _uvos_ | also thats open circut | 16:30 |
| buZz | _uvos_: batteryuniversity.com | 16:30 |
| _uvos_ | buZz they are wrong | 16:31 |
| _uvos_ | anyhow this is not the reason for the tresh anyhow | 16:31 |
| _uvos_ | the reason its so high | 16:32 |
| _uvos_ | is again because we take so long to boot | 16:32 |
| _uvos_ | we must guarentee that there is enough charge to boot again | 16:32 |
| _uvos_ | since mbm's tresh is too low | 16:32 |
| _uvos_ | btw the capacity below 3.2v is almost nothing | 16:33 |
| _uvos_ | your not loosing any real capcacity | 16:33 |
| _uvos_ | Wizzup: how do you define way to soon in this case | 16:34 |
| Wizzup | not sure, I'm wondering if there's some hw problem tbh | 16:35 |
| _uvos_ | ok | 16:35 |
| sicelo | iirc spinal reported faster boot times with leste+systemd ;-) | 16:36 |
| _uvos_ | also btw disregarding how bad 2.8v is for the batter | 16:36 |
| _uvos_ | d4 hw outright dies at that voltage | 16:36 |
| _uvos_ | if you try on lab psu | 16:36 |
| _uvos_ | no doubt | 16:36 |
| _uvos_ | systemd is way more efficant | 16:37 |
| _uvos_ | since its dosent have to execute scripts | 16:37 |
| buZz | yeah just run 28947923878923 binaries | 16:37 |
| buZz | what a improvement | 16:37 |
| _uvos_ | well perf wise it is | 16:37 |
| Wizzup | kinda ot | 16:38 |
| buZz | just distupgrade to debian then :P | 16:38 |
| buZz | weee finally found a random li+ charger | 16:39 |
| Wizzup | ok, let me see if I can fix the repodiff tool to be more useful | 16:52 |
| Wizzup | might rewrite it in python | 16:52 |
| buZz | yay charging works, at ~1A, also my droid4 now has -two- usb ports :P | 16:56 |
| buZz | https://imgur.com/a/BOGpG3n | 16:56 |
| buZz | just wedged cables under the screws for now | 16:57 |
| dreamer | hah. neat. I think I still have some of those modules around as well | 16:57 |
| buZz | 100% failsafe charging :P | 16:57 |
| bencoh | two ? | 16:57 |
| buZz | yeah, microusb on the device itself, second miniusb port on the images i linked | 16:57 |
| buZz | ;) | 16:57 |
| bencoh | it doesn't have d+/d- right? :> | 16:57 |
| buZz | indeed :P | 16:58 |
| buZz | that doesnt change the -port- though :D | 16:58 |
| bencoh | :) | 16:58 |
| bencoh | actually that's very handy for when you need to work with serial and still need it to charge | 16:59 |
| buZz | i'll just let this charge up for a couple hundred mAh | 16:59 |
| buZz | bencoh: these modules are sillycheap | 16:59 |
| buZz | and do 1A charging (but get quite hot doing so, fyi) | 16:59 |
| buZz | battery seems fine, not even heating up beyond roomtemp | 17:00 |
| buZz | there's a couple methods i think that can have this 'permanent' to fix any issues later when on the move | 17:00 |
| buZz | but, i'll just throw the right torq driver in my backpack , w/e | 17:00 |
| sicelo | Maybe the pogo pins (don't know if previous message went through) | 17:01 |
| buZz | afaik the pogopins arent on battery pins? but just to 5V? | 17:01 |
| buZz | not sure | 17:01 |
| bencoh | is that battery supposed to charge at 1A actually? | 17:01 |
| buZz | well, its eh, 1600mAh? | 17:02 |
| buZz | so even 1A would just be ~0.6C ? | 17:02 |
| bencoh | hm, yeah.... | 17:02 |
| bencoh | should be fine | 17:02 |
| buZz | 'typical liion' does 0.5C | 17:02 |
| buZz | 'expensive liion' can do 1C charging , and sometimes even up to ~5C discharging, pretty impressive | 17:02 |
| buZz | but the laptop ones are usually just 0.5C both ways | 17:03 |
| bencoh | did it trickle-charge at first? | 17:03 |
| buZz | bencoh: in the droid4? yeah at 50mAh :P | 17:03 |
| bencoh | :) | 17:03 |
| buZz | just 32 hrs to charge | 17:03 |
| buZz | :D | 17:03 |
| bencoh | :] | 17:03 |
| sicelo | If they do reliable charge from empty (pogo pins), I'll be happy, even if they don't go to battery directly | 17:03 |
| buZz | i'd wish kexecboot could just 'hang and charge' | 17:03 |
| sicelo | Yeah, that'd be great actually | 17:04 |
| buZz | that would solve all of these issues for all devices (that use kexecboot) eventually | 17:04 |
| sicelo | I tried the kexecboot shutdown trick ... works sometimes, but in some cases the d4 simply boots again. No idea why | 17:04 |
| buZz | depends whats attached on usb, for me | 17:09 |
| buZz | with the 'mode1' charger , it shuts down for me, with the 'mode2' it always reboots | 17:10 |
| buZz | well, 'usbdoctor' says 180mAh is inside | 17:10 |
| bencoh | usbdoctor ? | 17:12 |
| buZz | this; https://i.imgur.com/fHnb8VR.jpg | 17:12 |
| buZz | (i reset the mAh after this pic to 0 , it went up to 181mAh , now booting | 17:12 |
| bencoh | ah, that | 17:13 |
| buZz | its hanging on boot during 'waiting for power up request to complete' for md6600 | 17:13 |
| buZz | mdm6600*, is that the modem? | 17:13 |
| buZz | yeah | 17:14 |
| buZz | mayyyybe its not powering up because my sim still needs to be activated? | 17:14 |
| buZz | *removes sim for now* | 17:17 |
| buZz | *searches dumbphone to activate sim* | 17:19 |
| buZz | :D | 17:19 |
| bencoh | oh, that's interesting if that's the reason | 17:22 |
| buZz | actually, i think its cause there's a pincode on the sim? | 17:23 |
| buZz | why on earth would they ship it with that enabled :P | 17:23 |
| bencoh | in some parts of the world sims always ship with a pincode (or used to, at least) | 17:25 |
| buZz | horrible :) | 17:25 |
| buZz | and its even not '0000' or '1234' | 17:25 |
| bencoh | it's probably less common nowadays with all those smartphones | 17:25 |
| buZz | but some random nr you can only see on the whole simcard | 17:25 |
| buZz | yeah esim seems to be getting a lot more popular | 17:26 |
| buZz | ok! sim is activated and pin turned off | 17:28 |
| * buZz boots d4 with sim inside, lets see | 17:29 | |
| buZz | flies past where it first hang | 17:30 |
| buZz | annnnnnd hangs | 17:34 |
| buZz | with backlight/screen off, screen leds -on- , no response to powerbutton, keyboard, slider | 17:34 |
| buZz | drawing 0mA from USB | 17:34 |
| buZz | powerdown-voldown poweroff works , booting again | 17:35 |
| Wizzup | hmm | 17:35 |
| buZz | i expected https://leste.maemo.org/Development to have 'how to get -devel' :P | 17:40 |
| Wizzup | please add it | 17:41 |
| Wizzup | brb | 17:41 |
| buZz | added on https://leste.maemo.org/Development#Developing_on_a_device | 17:44 |
| Wizzup | hm my d4 just powered off without clear reason | 17:49 |
| Wizzup | maybe it really is some hw problem | 17:50 |
| Wizzup | battery is pretty much full | 17:50 |
| buZz | hmmm , 'apt install ofone' isnt a thing, i guess | 17:51 |
| buZz | eh, not sure, even apt search ofone doesnt fine anything? just some hashing algorithm | 17:51 |
| buZz | find* | 17:52 |
| buZz | oooo, 'ofono' | 17:53 |
| buZz | derp | 17:53 |
| Wizzup | why ofone? | 17:53 |
| Wizzup | oh | 17:53 |
| Wizzup | it dhould already be installed | 17:53 |
| Wizzup | (outside, hard to type) | 17:53 |
| buZz | ah, it is | 17:53 |
| buZz | but , i just wanna try out my simcard in leste | 17:53 |
| Wizzup | my d4 turned off again while trying to copy pstore, I guess it is battery re.ated | 17:54 |
| Wizzup | will try with serial later | 17:54 |
| buZz | Wizzup: maybe confirm the screws are well tight? | 17:54 |
| buZz | > For basic usage, there is the "ofono-scripts" package. | 17:59 |
| buZz | meh, nope | 17:59 |
| buZz | so eh, how can i get just cellular data working on this? | 17:59 |
| buZz | droid4 seems to negotiate 500mA charging, sad :) | 18:28 |
| buZz | my external charger is a lot faster ^_^ | 18:28 |
| bencoh | I'm not certain there is any real negociation if it settles for 500 :) | 18:43 |
| bencoh | negotiation* | 18:43 |
| freemangordon | bencoh: there is no, usb driver on d4 needs love | 20:05 |
| buZz | i'm not really aware how i can test or use my modem in droid4 :P i installed all the 'connui' stuff with 'cellular' in the name, but its telling me nothing is active | 20:16 |
| Wizzup | do you have libicd-network-ofono ? | 20:16 |
| Wizzup | that ought to power the modem | 20:16 |
| Wizzup | and potentially online it | 20:16 |
| buZz | i do not | 20:19 |
| buZz | *installs* | 20:20 |
| buZz | *reboots* | 20:20 |
| sicelo | buZz: development on a device? i wonder the -devel note doesn't belong somewhere else instead :-/ | 20:22 |
| buZz | any suggestions? | 20:23 |
| buZz | you dont feel -devel is for development? :P | 20:24 |
| sicelo | not necessarily 'development' on device :-) | 20:27 |
| sicelo | will look at wiki in a bit and make a suggestion | 20:28 |
| buZz | rebooting after installing the libicd-network-ofono got me a 'youfone' display at top and a 2G icon | 20:53 |
| Wizzup | buZz: sounds like you're connected to the network | 20:53 |
| buZz | anything i can do to get gprs data working? :P | 20:53 |
| buZz | was hoping https://leste.maemo.org/Status/Mobile_Data would tell me but alas | 20:53 |
| buZz | ah https://leste.maemo.org/Motorola_Droid_4/Modem | 20:54 |
| buZz | hmmm, dont think this is a userdoc | 20:54 |
| buZz | 15:21 < jonwil> Its also using /etc/gprs/icd-gprs-down.sh and /etc/gprs/icd-gprs-up.sh | 20:58 |
| buZz | i wonder ... | 20:58 |
| buZz | ok, doesnt seem that relevate :P | 20:58 |
| sicelo | buZz: just like on fremantle. just click the status, and choose your mobile operator :-) | 20:59 |
| Wizzup | buZz: no, it's much easier than that | 20:59 |
| Wizzup | like sicelo says | 21:00 |
| Wizzup | but the firs time will wait (it will connect, just reports ux fail) | 21:00 |
| Wizzup | if you try again in 10-15s it should succeed | 21:00 |
| buZz | click the status? eh | 21:09 |
| buZz | which status where? :P i cant click the 'youfone' up top, and on tapping the '2G' icon i dont see anything related, 'internet connections' also doesnt show gprs/gsm as a option | 21:10 |
| buZz | maybe its because of the connui*cellular* stuff i installed before? | 21:11 |
| Wizzup | buZz: status area | 21:13 |
| Wizzup | buZz: ok @ internet connections | 21:13 |
| buZz | i just get four 'icons' on statusarea tapping , 'battery' 'clock&alarms' 'profile' and 'internet connection' | 21:15 |
| buZz | which tells me 'not connected' although i can select wifi networks in there and it'll work | 21:15 |
| Wizzup | buZz: yeah so there ought to be a gprs related network where the wifi networks list is | 21:27 |
| Wizzup | btw, you know there's a meta pkg for all of this ight | 21:28 |
| buZz | i do not! whats it called? | 21:28 |
| Wizzup | hildon-connectivity-modile | 21:29 |
| Wizzup | it will get you connui-iapsettings-gprs amongst other things | 21:29 |
| buZz | 'depends on sphone but its not going to be installed' | 21:29 |
| buZz | 'depends on conversations but its not going to be installed' | 21:30 |
| Wizzup | it depends on conversations? hrm | 21:30 |
| Wizzup | buZz: do you have -devel ? | 21:30 |
| buZz | yeah | 21:30 |
| Wizzup | then it really should just install | 21:30 |
| buZz | from the 20220410 image | 21:31 |
| Wizzup | did you upgrade / dist-upgrade to be sure? | 21:31 |
| Wizzup | apt update && apt dist-upgrade | 21:31 |
| buZz | i installed a bunch of stuff with 'cellular' in the name that i thought was revelant | 21:31 |
| Wizzup | https://github.com/maemo-leste/hildon-connectivity-meta/blob/master/debian/control#L26 | 21:31 |
| Wizzup | well, try 'apt-get install conversations' and see where it whines? | 21:31 |
| sicelo | buZz: wait ... you're not coming from N900/fremantle? :-) | 21:32 |
| buZz | librtcom-eventlogger and libosso-abook | 21:32 |
| sicelo | and what package is this? 'depends on sphone but its not going to be installed' | 21:32 |
| buZz | sicelo: i've used em but not anywhere near long :P | 21:32 |
| Wizzup | buZz: those should be in -devel | 21:32 |
| Wizzup | what line did you use for -devel? | 21:32 |
| buZz | what i set on the wiki | 21:33 |
| buZz | https://leste.maemo.org/Development#Developing_on_a_device | 21:33 |
| buZz | i didnt leave the beowulf line, should i have? | 21:34 |
| Wizzup | the droid4 should only be there for droid4's of course | 21:34 |
| Wizzup | buZz: yes | 21:34 |
| buZz | oh, lemme do that then ^_^ | 21:34 |
| * Wizzup edits wiki | 21:35 | |
| buZz | oh | 21:35 |
| buZz | i just did | 21:35 |
| buZz | :P | 21:35 |
| buZz | ha!, with both those in 'hildon-con-mobile' gets >180 pkgs | 21:37 |
| sicelo | mostly translations? :-) | 21:37 |
| buZz | seems a lot of gstreamer, fluidsynth, v4l stuff | 21:38 |
| buZz | libharfbuzz, this is a fresh installed image | 21:38 |
| buZz | libwebkit2gtk :) | 21:38 |
| Wizzup | that's for conversations | 21:39 |
| Wizzup | well, no | 21:39 |
| buZz | alright | 21:39 |
| Wizzup | conversations in qt | 21:39 |
| Wizzup | in any case there's probably a reason for it :) | 21:39 |
| buZz | well i'm fine with whatever :P | 21:39 |
| buZz | installed, /me reboots | 21:43 |
| buZz | ok lets see :) | 21:49 |
| buZz | hmmm, dailing numbers works :) | 21:54 |
| buZz | but i still dont see a data setting in internetconnections | 21:54 |
| uvos | buZz: the pogo pins are conected to cpcap | 22:13 |
| uvos | buZz: the power ones anyhow | 22:13 |
| uvos | buZz: theres also 2 gpios | 22:13 |
| Wizzup | buZz: I need to dive into how that data connection is provisioned | 22:13 |
| Wizzup | freemangordon might remember | 22:14 |
| uvos | belcher: battery is supposed to charge at almost 2 amps | 22:14 |
| uvos | buZz: we dont negotiate any charging at all | 22:17 |
| uvos | it just takes 500mA (breaking spec) | 22:17 |
| uvos | you can have it charge at ~2A by setting the input current limit on the usb power supply in sysfs | 22:17 |
| Wizzup | btw I found some fishy dmesg in pstore regarding serial | 22:18 |
| Wizzup | I suppose we should upgrade to lates tkernel first | 22:18 |
| uvos | Wizzup: looks like buZz has the same problem as me with icd2 | 22:19 |
| uvos | wrt gprs | 22:19 |
| bencoh | uvos: isn't the charger supposed to prevent that (charging at more than 500mA unless negotation succeeded)? | 22:19 |
| uvos | bencoh: no | 22:19 |
| uvos | bencoh: never seen a charger that dose that | 22:19 |
| uvos | bencoh: some laptops do that tho | 22:20 |
| bencoh | I mean, the part that's plugged to the pc/wall | 22:20 |
| buZz | Wizzup: ooooo it just appeared! | 22:20 |
| bencoh | hmm | 22:20 |
| buZz | after 3/4 reboots | 22:20 |
| uvos | also you have to negotiate for 500mA too | 22:20 |
| uvos | you get 100uA or something like that | 22:20 |
| uvos | without negotiating | 22:20 |
| uvos | i remember powerpc imacs where anal about that | 22:20 |
| bencoh | that one is just ignored almost everywhere yeah | 22:21 |
| uvos | yeah | 22:21 |
| uvos | cpcap is alos very serious about that | 22:22 |
| uvos | (in otg mode) | 22:22 |
| buZz | how can i get 'Contacts' ? like https://maemo-leste.github.io/images/contacts.png | 23:16 |
| buZz | lol, all osso-addressbook-l10n* packages are installed, but -not- osso-addressbook itself :P | 23:28 |
| Pali | Wizzup: Hi! Have you looked at that n900 u-boot DM serial patch? | 23:30 |
| buZz | do i need 'telepathy' ? seems osso-addressbook really wants it | 23:32 |
| Wizzup | Pali: do you have a mail subject for me? | 23:35 |
| Wizzup | buZz: yes you need the framework | 23:35 |
| Wizzup | freemangordon: new tooling: https://dpaste.com/FC2WFR7AA.txt and https://dpaste.com/8UDESJGQT.txt | 23:36 |
| Wizzup | I made it operate mostly on source package versions | 23:36 |
| buZz | would be nice if apt install osso-addressbook pulled that in :P | 23:36 |
| Wizzup | seems better than the way the curren ttooling works | 23:37 |
| Wizzup | buZz: what is the behaviour you see? | 23:37 |
| buZz | eh not sure, i rebooted and it went away ;) | 23:37 |
| Wizzup | Pali: [UNTESTED PATCH] Nokia RX-51: Convert to CONFIG_DM_SERIAL ? | 23:37 |
| Pali | yes! | 23:40 |
| sicelo | and there was another from tmlind .. (something related to OFF mode iirc) | 23:44 |
| buZz | hmm funny, cant -start- a conversation in conversations? :P | 23:49 |
| buZz | and not sure how i can get it to use the contacts i have in osso-addressbook | 23:49 |
| Wizzup | Pali: I will test tomorrow | 23:49 |
| Pali | ok! | 23:50 |
| Wizzup | I have everything here now | 23:50 |
| Wizzup | do I apply it on latest u-boot master, or some rc? | 23:50 |
| Pali | master should be ok | 23:52 |
| Wizzup | ok | 23:54 |
| Wizzup | I'll boot master without the patch first, see if it works, and then apply the patch and report back. | 23:54 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!
